
Re: A SWATH vs. TWX challenge
Mongoose wrote:
It's probably the most CPU-intensive thing a helper does.
Parsing courses is no where near as CPU-intensive as actually calculating them from a map.
Mongoose wrote:
IO includes network and disk access. These are the main things limiting any script. Not CPU.
IO is disk access and RAM access. Network speed is latency. IO is not a big problem in my scripts. CPU definitely is.
Mongoose wrote:
I doubt that. It would have to be a pretty contrived benchmark to single out the CPU, i.e., working on a large amount of data in RAM without making any use of the database or the network. What scripts have you written that do that?
Bubble searches, traffic analysis, optimal course searches, array sorts, etc, etc.
Mongoose wrote:
About the only thing I can think of would be a bubble finder or some sort of traffic analysis. (If the entire database is cached, it would eliminate disk IO... but even then, SWATH is hindered by JNI and puts in a good showing despite that.)
Generally, yes, I cache the database into a set of arrays. In fact TWX proxy automatically caches the entire database if you let it.
Mongoose wrote:
What kind of script do you think would make a good benchmark?
I think a wide variety of scripts would be a better approach. ZTM, world SST, bubble stuff, traffic analysis, sorts, etc. If the goal is to honestly compare the speed of both, why not do exactly that?