6 commits

Author	SHA1	Message	Date
Griatch	047de533f3	Moved dummyrunner into a separate directory under src/utils	2012-09-03 21:54:13 +02:00
Griatch	f68523cc22	Minor optimizations and some fixes to the dummyrunner.	2012-08-22 22:34:43 +02:00
Griatch	4678234e9a	Multiple fixes to ev and utils: ... Made utils.variable_from_module more generic (it can now load pretty much any form of module it's given and also supports searching and returning multiple variables). Removed the variable-load functionality from utils.load_module; this is now purely a loader - use variable_from_module instead. I found out that one couldn't import from src.commands.default due to the __init__ file being restrictive for the sake of the ev API. Removed that and instead imported the default commands into ev.py with the help of utils.variable_from_module instead. Some more fixes in ev followed on this.	2012-04-22 12:23:42 +02:00
Griatch	ab2ba19782	Fixed critical typo in instructions for dummyrunner.	2012-02-22 15:15:32 +01:00
Griatch	fd857f5c86	Expanded the dummy runner, making it more realistically mimicking real Players by spreading out its access usage.	2012-02-22 12:44:51 +01:00
Griatch	f306c5a6a2	Added a separate program for launching client connections. Meant mainly for server devs at this point. It is primarily useful for stress-testing so as to get profiling data using e.g. cProfiler - running many clients with a short timestep -will- slow the server to a crawl! If using sqlite3 with 50+ clients you will also see the memory consumption gradually - our sqlite3 setup runs in RAM by default and these things create a lot of new stuff every timestep - make sure to shut it down before you run out of memory! Not sure if this says much about the server's actual behaviour with many players at this point, the usage pattern is hardly "realistic". Also, it's usually better to shut down the server before the dummyrunner.	2012-02-05 17:58:00 +01:00