On Jan 3, 2008, at 9:45 AM, Evan Weaver wrote: > > * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA, > Rack...)
merb, rails, camping, nitro, rack > > * Mongrel version 1.0.1 thru 1.1.3 > > * Mongrel handlers used (rails, dirhandler, camping, cgiwrapper...) rails, dirhandler,upload_progress_handler,secure_download, many more custoemr handlers > * How many mongrel routes and handlers per route registered (if you > don't know, it's probably <= 2) up to 15 max. usually 2-4 > > * Any Mongrel plugins used (mongrel_upload_progress, mongrel_gzip, > mongrel_cow_cluster, mongrel_experimental...) mongrel_upload_progress, mongrel_gzip > > * Mongrel runners used (mongrel_rails, mongrel::cluster, > mongrel_service, RV, others... please be *very specific* about which > options of the runner you use. For example, some people use > mongrel::cluster but only for the --clean functionality, not for the > clustering). mongrel_cluster but only for the --clean option. woudl love to see -- clean in mongrel itself so i no longer need mongrel cluster. > > * Number of mongrels per server per app 3-25 per server, usually closer to 3-5 per cpu core > * Monitoring system (runit, monit, god...) monit, god , nagios > > * Proxy or software loadbalancer, if any (apache mod_proxy_balancer, > nginx, pen...) Nginx, swiftiply, apache, haproxy > * HW loadbalancer, if any (Netscaler...) coyote point equalizers, Linux LVS load balancers. > > * Caching strategy (memcached fragments, memcached object, squid, > rails page cache, rails page fragments, ESI) page caching, fragment caching on GFS filesystem . memcached fragments and sessions and caches. > > * Whether you serve media assets via mongrel itself, as opposed to > through a webserver via nginx > * Operating system including distribution or version (OS X 10.4.10, > Ubuntu/Linux 7.10, WinXP SP2, OpenBSD 4.1...) custom variant of Gentoo linux > * Architecture, via 'uname -a' preferably (x86, x86_64, Sparc, PPC, > Arm (ha), JRuby) Linux ey00-s00141 2.6.18-xenU #1 SMP Fri Jun 15 17:50:34 PDT 2007 x86_64 Dual Core AMD Opteron(tm) Processor 265 AuthenticAMD GNU/Linux and Linux ey01-s00141 2.6.18-xenU #1 SMP Fri Jun 15 17:50:34 PDT 2007 x86_64 Intel(R) Xeon(R) CPU E5345 @ 2.33GHz GenuineIntel GNU/Linux > * CPU count Hmm... lets see here. somewhere around 400 ? > > * Ruby version including custom distribution patches, > (1.8.6p110+threadhooks, 1.8.5, JRuby 1.1b1, Rubinius trunk... also > note where you got it, in case it isn't clear, for example, OS X 10.5 > built-in, Ubuntu apt, Instant Rails, direct compile from source) > * Rubygems (yes/no, version) 1.8.5 from gentoo's portage 1.8.6p111 from portage > Please mention anything else about your system that's kind of weird, > and anything that's been particularly troublesome regarding mongrel > deployment. Please let's add --clean to mongrel itself. Other then that the only thing might be to add some additional logic to the gracefull shutdown of a mongrel server. Say if it tries to reap old threads for more then 30 seconds, just have it terminate violently. > Cheers- - Ezra Zygmuntowicz -- Founder & Software Architect -- [EMAIL PROTECTED] -- EngineYard.com _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
