-
Notifications
You must be signed in to change notification settings - Fork 924
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bytes to kilobytes, megabytes etc #312
Comments
+1 |
1 similar comment
+1 |
+1 |
Hi All, For your parameter e.g. number of bytes of memory used called ‘avgRSS’ one can create a scripted field in Kibana with the following formula: name of the scripted field: avgRSS_main_reco This corrects for the wrong binary conversion factor finally using decimal one in line with the decimal unit labels. It carries with it the inconvenience, that one has to be alert in case Kibana fixes the issue in the future. but as far as I have heard, this is not going to happen anytime soon (problem located in one of the upstream libraries). Also, Kibana applies this correction factor per-document-value, i.e. it will not show a correct number after aggregation ! Another option, less elegant, but functional is : Cheers, PS: for general n-core jobs e.g.: (doc[‘avgRSS'].value/doc['ncores'].value) * pow(1.024, ln(doc['avgRSS'].value/doc['ncores'].value)/ln(1000)) |
1.5.6 added a new format you can use |
|
The conversion is not in line with the International System of Units.
Currently Numeral-js converts 1024 bytes to 1 Kilobyte (kB) but 1024 bytes has officially been a Kibibyte (KiB) since 1998
1000B = kB (kilobyte)
1000000 = MB (megabyte)
1000000000B = GB (gigabyte)
1024B = KiB (kibibyte)
1048576B = MiB (mebibyte)
1073741824 = GiB (gibibyte)
Most operating systems file managers have been updated to report the size as defined in the standard.
Is there any chance that Numeral-js will be updated ?
The text was updated successfully, but these errors were encountered: