Modules and performance
Posted: 28 Nov 2015, 17:41
Now that I have Porteus+VirtualBox-on-a-stick up and running, I'm looking into tying some loose ends. Here are two questions but I'm afraid more will follow:-)
1. Number of modules in /modules and overall performance : does the module concept scale well, ie is a Porteus install with say, 30 modules in /modules almost as fast as a Porteus install with only 5? If there's a significant performance hit, it'd probably make sense to merge modules into one or more bigger modules packs (I've just found mergexzm, a script which does that... this actually triggered that question). Perhaps there's even a practical upper limit for the number of modules.
2. Is the save.dat file basically structured like a module? If so, I could clean it up and move the whole thing (or those parts that do not change) to /modules. In what sequence are those modules loaded?
1. Number of modules in /modules and overall performance : does the module concept scale well, ie is a Porteus install with say, 30 modules in /modules almost as fast as a Porteus install with only 5? If there's a significant performance hit, it'd probably make sense to merge modules into one or more bigger modules packs (I've just found mergexzm, a script which does that... this actually triggered that question). Perhaps there's even a practical upper limit for the number of modules.
2. Is the save.dat file basically structured like a module? If so, I could clean it up and move the whole thing (or those parts that do not change) to /modules. In what sequence are those modules loaded?