Tiny Core Extensions > TCE Talk
upx for large executables?
hiro:
it's not sure what kind of "ram usage" this is measuring.
but i presume it's most likely during bullk extraction of the whole fine (which we do not do), and not the one we actually care about (ram overhead due to block overhead).
though now that i think about it, i don't even know whether either of these ram usages would actually be significant enough for us to even begin bothering about, versus for example performance effects (due to large block access overhead/inefficiencies during actual smaller partial block highly random access scenarios for example).
less third-party random numbers, more first-party testing please. and explain your numbers.
GNUser:
--- Quote from: hiro on May 17, 2024, 07:37:43 PM ---it's not sure what kind of "ram usage" this is measuring.
--- End quote ---
Good point, hiro.
At the end of the day, the amount of effort in benchmarking and defining terms might be much greater than the technical gains.
hiro:
if you try it and the benefit can be felt even without careful measurement, then it's likely worth measuring to optimize further down the same route.
in other words: if you find hints, it's good to use that newly found knowledge and investigate further and try to understand the full situation ;)
CardealRusso:
--- Quote from: hiro on May 17, 2024, 07:37:43 PM ---it's not sure what kind of "ram usage" this is measuring.
--- End quote ---
This is the total RAM usage of the system, with different algorithms and block sizes for ungoogled-chromium. This is the memory usage of a fresh start of the system, without running any program other than top.
It's not very accurate, but it definitely gives us some idea.
hiro:
tested on tinycorelinux?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version