On Tue, Nov 25, 2014 at 5:16 AM, Andre Garzia wrote:
> co-routines
mmm, co-routines...
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.
Eons ago I created a library to do FastCGI from LiveCode. Even though my
library supported multiplexing stuff LiveCode could not respond to more
than one user at a time. If LC was multithreaded or had co-routines or
fibers or whatever lightweight gizmo they could create in Scotland to let
us run mo
The benefit of FastCGI would be that the Fast cgi instance would always be
running and would not need to be restarted every time a .lc script is
parsed saving on the execution time.
Even as a CGI process, LiveCode should already be able to run behind a load
balancing server,
Kind Regards
Simon
O
Hi Andre
I agree with your comments on the appropriateness of the tests. I’ll give some
thought to incorporating more I/O based tests.
Do you think that having FastCGI support so that LiveCode could be run behind a
load balancing server would be an improvement from a scalability point of view.
Geoff
Thanks for your input.
I think you are correct that the memory access comparison isn’t fair. I don’t
have time right now but I’ll try to come up with a better comparison.
I’m not convinced that the file comparison is fair. If LiveCode is appending
the data to the file rather than overwr
Hi Peter,
Thanks for your testing!
I think we're approaching this performance issue wrong. Most webapps will
be I/O bound and not CPU bound. Calculations are not the most common thing
going on but I/O in the sense of reading and writing from database and
files are. Also the only way to deal with
My PHP is weak, but if the memory access test is a regular array, then
comparing it to a livecode array is somewhat apples and oranges, since LC
is really a hash. But on the other hand, there's no way to do a simple
array in LC, so it's not like you can do better.
For the file access test, your te
In a previous email Richard Gaskin, the LiveCode Community Manager, wrote
"Given the role of memory and performance for scaling, if we want to see LC
Server taken seriously as a professional server tool we need to identify and
eliminate any significant performance difference between it and PHP.”