[ultimape]

Cpu limit likely means you are doing an inf loop, at least in my experience.

Its also possible that their rate limiter is not tied to the performance of the system, but rather to the wall-clock. Given that the simulator runs in the local browser, there would be a lot of variability in this kind of thing.

For my ant simulator, I'm focusing heavily on performance testing and instrumentation for precisely this reason. Having to adapt to various browsers means you need to have some pretty tight metrics.

Performance in the browser is an interesting problem. I've seen some advanced libraries rely on Acorn.js - a JavaScript based JavaScript interpreter - because its faster than some built in JS bits on older browsers in regards to processing large amounts of JSON. Boggles the mind.

Once this thing gets up and running, I doubt the limitations of the browser's runtime will be an issue since it will be relying on node.js on some type of cluster server.

I'd really love to dig into this thing on my own. I hope they get funded and start hiring.