EBo wrote: > Other than that Python is nice for development and portability, but at > the cost of speed. And before we get to far down the speed wagon > discussions -- define just how much speed you have to have instead of > demanding that it always be as fast as it can be. > I did some torture testing for a potential customer a long time ago. The test was a 2" circle of 10000 G01 moves. On a 600 MHz Pentium II (or would that have been a PIII?) I got some 780 blocks/second. I have no idea how much of that was due to the interpreter and how much in the trajectory planner. Also, it was not clear how much was due to raw processing speed and how much due to the 1-block lookahead. Much of this experiment was to see what the G64 Pxx could do for contouring work.
Well, I think even a 3:1 slow down would not be a good thing, unless the interpreter is a TINY part of the total block processing time (which it may well be, I just don't know.) Jon ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
