... | ... | @@ -3,6 +3,21 @@ |
|
|
# My SION files are HUGE! What can I do?
|
|
|
See [SION File Defragmentation](Usage#sion-file-defragmentation). Note that you can still load the defragmented SION file into python, see [Linktest Python Reader](Linktest-Python-Reader), and it can still be used to generate reports, see [Linktest Report](Linktest-Report). After defragmentation the file can be further compressed using any non-lossy compression tools. The resultant compressed file can no longer be loaded into python and hence reports based on it cannot be generated unless the file is decompressed first.
|
|
|
|
|
|
# What do the weird unit prefixes, like ki, Mi and Gi, mean?
|
|
|
These are the prefixes for binary sizes, which use a base of 1024 ($2^10$), stipulated by the International Electrotechnical Commission (IEC) and accepted as an international Standard by the International Organization for Standardization (ISO) in Standard ISO 80000. They use the nearest multiple of 2 to the common Système International d'unités (SI), now known as metric prefixes, which have a base of 1000.
|
|
|
|
|
|
Here is a comparison table between the two standards:
|
|
|
|
|
|
|Metric|Value|Binary|Value|Ratio B/M|
|
|
|
| --- | --- | --- | --- | --- |
|
|
|
|NONE|$`10^0`$|NONE|$`2^0`$|1.000|
|
|
|
|k|$`10^3`$|ki|$`2^{10}`$|1.024|
|
|
|
|M|$`10^6`$|Mi|$`2^{20}`$|1.049|
|
|
|
|G|$`10^9`$|Ti|$`2^{30}`$|1.073|
|
|
|
|T|$`10^{12}`$|Gi|$`2^{40}`$|1.100|
|
|
|
|
|
|
A common problem with these unit prefixes is that they are equated to metric prefixes, however, for larger units the difference between prefixes grows substantially as indicated in the fifth column of the table, which shows the ratio between the different corresponding prefix values. Lesson to learn, do not equate these prefixes!
|
|
|
|
|
|
# I am running a latency test and the first row in my timings matrix is much slower than the others. What can I do?
|
|
|
TLDR: You likely forgot to use warm-up messages.
|
|
|
|
... | ... | |