To check the load of a server there is a common technic from Linux. Checking the number of used processes gives no information about the load. You can simple check the load if you run "uptime" in command line interface. The result you get displayed gives you more information about the load, but on shared hosting it is difficult to measure the load, because you are not the only one who causes load.
some statistics about "magic" option cache storage:
- without "magic" option full recache for 5(five) UAs for 9000 products: 60GB
- with "magic" option full recache for 18(eighteen) UAs for 9000 products: 22 GB
To explain what seems to be "magic" related to the disk space, here are some additional information. First of all what @AndreyPopov found out is not magic. LiteSpeed only forgot to add a default curl option in code. This option has affect on how cache files are stored. If this option is set it will compress the cache files and as everybody knows compressing will reduce the file and the disk space. This simple public option reduces the disk space dramatically.
This is not an accepted method. It differs from server to server and depends on many facts. Value "100" can be everything, but gives no information about if a server is overloaded or in idle mode. Why don't you accept what is "law"?
Because nobody can accept it for his own use. Your load is related on your server but each server has different ressources. That is why Linux offers a method to check it really, but always related to the used server with different power.
As long you don't acceppt other advices you will never be an expert for caching and for improvements for faster cache wamup. For your information I developed a lot of applications for LScache and for warming the cache. In comparison to me your are a Newbie without knowing what he is doing.
this is NOTHING matter.
because you hear only yourself.
all our discussions here you only can say: you are wrong, you are wrong.
but ...... LS developers have another point of view and ADDall my ideas and founded problems to code.
and all your "help" only bla-bla-bla-bla: I'm great crawler developer