Thanks for all the feedback. I'm going to check out everything everyone mentioned except maybe the Twitter stuff because 1 out of every 6 times I access a Twitter page I get an "over our capacity" apologetic error message. Jk, I'll still check it out. On an exciting note, it turns out that I have dramatically underestimated raw ColdFusion / Java performance. On my desktop workstation: Vista 64 Business w/ a single 2.83 Ghz Core 2 Quad, throwing a measley 4 of my 8GB at the JVM heap, ColdFusion is able to randomly access any key of a single, 2 million+ randomly-keyed (w/ symbols!), application-scoped struct w/ minimum length values of " domain.com/rhxwianjuoavrgjk" in 0 milliseconds per read, even with multiple browsers simultaneously accessing the page repeatedly ( which requests 20 or so of the random key values per serve ).
Checking out the cost in the Server Monitor, that entire struct is using just under 40MB of RAM. I cannot even believe how ridiculous that is. 0 milliseconds. None. Zilch. If ColdFusion were a young woman, I would be whistling like a sailor right now. On Thu, Mar 12, 2009 at 4:41 PM, denstar <[email protected]> wrote: > > On Thu, Mar 12, 2009 at 3:52 PM, David McGuigan wrote: > ... > > Assuming I have a highly-capable server ( ex: 128GB of RAM or more and > two > > quad core Xeons with standard 15k RPM drives ) and that both the database > > and the application servers are running on the same box and sharing the > same > > hardware... > > Ouch. If you need to have redundancy, one server isn't going to cut > it, especially if you've got appserver/db/webserver(?) running on the > same box. > > Servers are pretty cheap these days ($4,500-$5,500), so IMHO I'd go > for a "tiered" approach, meaning, split out your app server(s), your > db server(s), and your webserver(s). > > Virtual Machines can do some of this for you, which means you don't > need as many physical boxes, but you still want to have at least a > couple physical boxes, in case of hardware problems (ideally you'd > want the physical servers in different locations, even, in the Perfect > World-- or get some super-host type deal, who does all this crap for > you;]). > > JBoss has some pretty tits caching stuff built right in, much of it > geared for High Availability, so you might want to look into that, and > a lot of people are buzzing about "cloud" computing (Amazon, etc.), > which might be a slick option, depending on your context. Twitter has > been pretty open about how they've scaled things, and trying to use > the cloud (latency was an issue, IIRC)... looking at how others have > approached the problem can only help. > > A lot of it depends on your context tho (what kind of content you > mostly serve, the amount of control you need, amount of cache > updating, as it were, etc.), so... well. Eh. > > I'm no expert, so, take all this with a grain of salt-- if there is > one thing I know, it's that there are many means, to to the ends. > > Well, that, and JMeter ROCKS! ;) > > -- > (He's got the monkeys, let's see the monkeys) > - Aladdin (Prince Ali song) > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
