On Feb 23, 11:59 pm, "alex clemesha" <[EMAIL PROTECTED]> wrote: > First off, thanks for doing those benchmarks, > they are pretty interesting to see! > > I want to stress that I think that this API discussion > should really *not* have anything to do with speed, > and this is precisely because of the use case of the API: > > Users evalute cells one at a time, not 625 times in 1 second ;) > > The above is not meant to be precise in any way, > just to kind of express the issue we are dealing with here. > If both methods allow a cell's code to be transfered in > sub-second time, let's aim for functionality, not speed.
That's not MY use case... One of my first potential uses of this API would run in a mouse-motion handler, so it would trigger an API call ideally every time the mouse moved. Running the loop at 10Hz would probably be acceptable, but 50Hz would be better; and most of that time should be allocated to computation and drawing, not communication. So the sage.math XMLRPC timing above (1.38 ms) would probably be fine, but the OSX timing (43.7 ms) would be a pretty huge bottleneck... Carl --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
