Hi!
The list below could be mine, it's exactly as I feel about
AOLserver/Apache.
UTF handling in TCL is, as it's meant to be. We're launching new sites
on a regular basis and have to import from a lot of 3rd party systems
(SAP, Peoplesoft, homegrown ERPs, multimegabyte XML files, gigabytes per
day of xml data via socket connections, Excel sheets, CSV, ...) The TCL
character encoding can handle them all, even if the feeds are sometimes
a real mess, with mixed encoding, wrong stated encoding or the horror
that are windows encodings.
We also use the nsv_* procs for localization, with millions of strings
in the database for display and on the fly translation for admins, for a
high performance multicast system, and for our websocket streaming which
can handle at least ten thousand clients. We never had a problem, it's
fast, reliable and easy to use.
Performance is really fantastic. We had an Apache reverse proxy sitting
in front of a big AOLserver site. When we hit sustained 200 pages/sec
the system broke down. We tried to improve the AOLserver performance,
until we noticed that it was Apache which could not cope with the load.
So we switched to nginx and the system has been working fine for more
than a month now. AOLserver did all the heavy lifting and still Apache
was the bottleneck.
Scaling ist great, too. We have servers with lots of memory, where we
can cache nearly the whole (postgres) database in memory. Disc IO is
negligible and works over a pretty fast fiber channel SAN, so the scarce
ressource is CPU power. We noticed over the last few years, that
throwing raw CPU power, be it fast processors or lots of cores, will
improve the AOLserver performance nearly linear. With Apache/PHP,
Apache/Java or IIS/ASP.net (shudder) not so much, to state it in
friendly terms.
I also would mention the fast startup times of AOLserver as an
advantage. When you've ever tried to restart an Apache/Tomcat/JBoss
site, you really get to value the difference of a startup time of
seconds rather than minutes.
The only problem we have is similar to Johns occasional crashes. But I
have 2 test servers and 1 pre production server, where AOLserver crashes
with " Fatal: received fatal signal 11" or "alloc: invalid block:
0xc595660: b0 6", somtimes even 4 or 5 times while starting up. Nearly
the same code works for other very similar installations with much
higher load.
Wolfgang
Am 2012-09-27 23:44, schrieb John Buckman from BookMooch:
On the apache vs aolserver topic, I just want to mention that we've
been migrating sites *off* of Apache/PHP/Perl, and onto aolserver, for
the past 2 years.
http://moodmixes.com/ was launched last year,
http://ilicensemusic.com/ a few weeks ago, and we're currently
rewriting http://magnatune.com/ to be all-aolserver.
http://bookmooch.com/ has been all-aolserver for 7 years, and while we
had to learn a lot to get to scale, once we got there it's been
totally reliable.
The reasons we're moving to aolserver:
1) proper threads, and shared caches make certain features really easy
and very reliable (such as multilanguage support, much faster
memcached-like features)
2) the UTF handling in aolserver/tcl is really solid, but
frustratingly weird in apache/PHP
3) very, very reliable
4) very fast
5) massive code reuse in practice, crazy fast productivity
6) scales fantastically on multicore server with lots of memory
7) the C integration is so easy
8) no security / malware problems
The two major problems I've had with aolserver over the past two years
are:
1) very occasional crashes
2) memory bloat, probably caused by temporary creation of large tcl
data structures, that doesn't get ever freed
-john
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
--
digital concepts OG
Software & Design
Landstrasse 68 / 5. Stock
A - 4020 Linz
Büro: +43 732 99711772
Mobil: +43 699 19971172
------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
