![]() implemented ability to add custom plugins.improved notifications about hitting LVE limits (more informative and without false positives).lvestats-server saves “snapshots” of user’s processes and queries for each “incident” - added new lve-read-snapshot utility.lvestats-server emulates and tracks faults for CPU, IO, IOPS.CPU usage is calculated in terms of % of a single core (100% usage means one core).Old LVE-statistics functionality is hard to extend.Notifications in old LVE-statistics are not accurate because they are based on average values for CPU, IO, IOPS.what processes are running when user hits LVE limits.Example Old LVE-statistics does not provide a way to determine a cause of LVE faults, i.e.On 32 core servers usage is not visible for most users (as they are limited to 1 core). 100% CPU usage in old lve statistics means “all cores”.So, such peak load will noExat be recorded and we need to store data with much higher precision. Data in old LVE-statistics is aggregated to 1-hour intervals. If user used 100% of CPU for 1 second within an hour, it is only 1-2% for a minute, and 0 for 5 minutes. ![]() Old LVE-statistics store averages as integer numbers, as % of CPU usage.What features will be implemented in the future?. ![]() # General information and requirements # LVE-Stats 2 # General information and requirements
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |