Up to around 500 or so while maintaining a decent framerate (say, better than 30FPS in steady state). I was using Java's Processing though - which I would expe

Up to around 500 or so while maintaining a decent framerate (say, better than 30FPS in steady state). I was using Java's Processing though - which I would expect to be considerably faster than Processing.js. I didn't try decoupling the UI from the computation/model (since the performance was already more than sufficient for my needs), but my gut tells me that my physics code was the bottleneck - not Processing itself.