Quote:
Originally posted by mryellow
The RAM storage just brings up the response speed and allows
us to process more hits on less database connections. Hits are
moved from RAM to the database, just not a real-time connection
for every single surfer that hits the page.... Different to most
trade programs which are restricted by the volume MySQL can
take (MySQL is a very poor database server compared to say
Oracal). All the trade parts are coded in fast efficient C code and
will have FastCGI code added shortly which will make the whole
thing run as fast as an Apache module, using only 1 process on
the server.
Spent a lot of time planning this system and designing it to be
the fastest and most scalable trade script ever seen. From the
ground up it's quite different to other solutions, however it's still
based on tried and tested methods.
I'll drop in tomorrow again, getting a bit late for now.
-Ben
|
Have you ever considered coding in Python? In some articles/benchmarks I've read, it is faster for interacting with MySQL than C code. It's a language that is basically taken from parts of C and parts of PHP.