Changes between Version 6 and Version 7 of nebulous-performance-analysis
- Timestamp:
- Feb 17, 2011, 12:30:10 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
nebulous-performance-analysis
v6 v7 16 16 [<timestamp>_<Nebulous messages>_<Apache errors>_<Create>_<Find Instance>_<Delete>_<Fail Stat>_<Stat>_<Other Nebulous>_<Non Nebulous>] 17 17 18 <timestamp> is in ISO8601 format YYYY-MM-DDTHH:MM:SS. The utility convert_date_iso_to_int.py (in the same SVN repository) can be used to convert it to YYYYMMDDHHMMSS that is surprisingly an integer value chronologically ordered and that can be used as an input value for gnuplot).18 * <timestamp> is in ISO8601 format YYYY-MM-DDTHH:MM:SS. The utility convert_date_iso_to_int.py (in the same SVN repository) can be used to convert it to YYYYMMDDHHMMSS that is surprisingly an integer value chronologically ordered and that can be used as an input value for gnuplot). 19 19 20 <Apache errors> can sometimes be -1. It means either that no data was available, or that there was no entry in the error_log file for the 10-minute sampling period. The distinction is not made because 1) it will require to add more code (I let you guess all the cases that may occur); 2) once plotted, the average human will not mage any difference between -1 and 0 (specially when values as large as 1000 are drawn).20 * <Apache errors> can sometimes be -1. It means either that no data was available, or that there was no entry in the error_log file for the 10-minute sampling period. The distinction is not made because 1) it will require to add more code (I let you guess all the cases that may occur); 2) once plotted, the average human will not mage any difference between -1 and 0 (specially when values as large as 1000 are drawn). 21 21 22 22 Note: parsing log files can last LONG (Rule of the thumb 1 hour for 1 million lines for ippc00 (RAM 32G/IntelXeon 2.4Ghz, cache 6M, no RAID?). If you find the law, write it down)
