tree c1d163dfff53dfc3052b17441e7cc20890efa183
parent fedc20991d1cae2d89741dce5788e2042da639c6
author 吴晟 Wu Sheng <wu.sheng@foxmail.com> 1659958738 +0800
committer GitHub <noreply@github.com> 1659958738 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJi8PXSCRBK7hj4Ov3rIwAAtVQIAKNMiMVt0DQ+9XIlilHwR7f0
 4puh7wcthICEIBsdejlC5oILEfbJxZG47+DsqhlULgWcy2p07wGdrjHwo5wthZ57
 j46WQaHF6nXbrTahbpc87NrVA13iTrqmX5iNndZW1tnO/GmueUyAKVwpHymMDgOK
 FotB8vX0UZC5iOjKC1EcaoVm7mTfwNEnH0V6OsQxTmi3zXnbDCbQcNtPOwlcS8mY
 L87IlwCDAQG4bJ316D0iG4jsZwr2eabjf+MskIyn7OC6tWTS348Rg0pLZuT5l1G/
 +KG1tqdZXugbIMtJCH05NpFDKV17IYQXBAp8df5F0zi4+dNAnMCwK2wgCFZj8Xs=
 =t97a
 -----END PGP SIGNATURE-----
 

[Critical] Fix a low performance issue of metrics persistent in ES (#9437)

[Critical] Fix a low-performance issue of metrics persistent in the ElasticSearch storage implementation. One single metric could have to wait for an unnecessary 7~10s(System Env Variable SW_STORAGE_ES_FLUSH_INTERVAL).

This is a solid and critical performance issue, from the self-observability metric, we could find one metric that would need 7-10s to execute the data flush, which is not expected.