Inspiration for Stack Overflow occasionally comes from the unlikeliest places. Have you ever heard of the dating website, Plenty of Fish?
Markus Frind built the Plenty of Fish Web site in 2003 as nothing more than an exercise to help teach himself a new programming language, ASP.NET. The site first became popular among English-speaking Canadians. Popularity among online daters in many United States cities followed more recently, and with minimal spending on advertising the site. According to data from comScore Media Metrix for November 2007, Plenty of Fish had 1.4 million unique visitors in the United States. In December, Mr. Frind said, the site served up 1.2 billion page views, and page views have soared 20 percent since Dec. 26.
The actual plentyoffish.com site design, although it has improved (believe it or not) since the last time I looked, is almost horrifyingly bad; it literally looks like a high school student's first website programming attempt. But it doesn't matter. The site is a resounding success with users, to the point that it is almost completely user-run:
No one heads to Plenty of Fish for the customer service, which is all but nonexistent. The company does not need a support structure to handle members' subscription and billing issues because the service is entirely advertising-based. Its tagline is: "100 percent free. Put away your credit card." For hand-holding, users must rely on fellow members, whose advice is found in online forums. The Dating & Love Advice category lists more than 320,000 posts, making up in sheer quantity what it lacks in a soothing live presence available by phone.
Granted, comparing a dating site to other online properties is kind of unfair. As I mentioned in an earlier post, the most sustainible and enduring business models either get you laid, or get you paid -- and the more directly the better. Jamie Zawinski's classic Groupware Bad article covers the same ground:
So I said, narrow the focus. Your "use case" should be, there's a 22 year old college student living in the dorms. How will this software get him laid?
It's pretty clear which axis of human needs Plenty of Fish tends to. It's already working with way more cheese than most software developers will ever have.
OK, so Markus Frind singlehandedly built a massively popular free dating site that is almost entirely community run. Big deal. But what makes it especially incredible is that he does it all on a handful of servers:
- 1.2 billion page views per month, 500,000 average unique logins per day
- 30+ million hits per day, 500-600 per second
- 45 million visitors per month
- top 30 site in the US, top 10 in Canada, top 30 in the UK
- 2 load balanced Windows Server 2003 x64 web servers with 2 Quad Core 2.66Ghz CPUs, 8 GB RAM, 2 hard drives
- 3 database servers. No data on their configuration
- Approaching 64,000 simultaneous connections and 2 million page views per hour
- Internet connection is a 1 Gbps line, 200 Mbps is used
- 1 TB per day serving 171 million images through Akamai
- 6 TB storage array to handle millions of full sized images uploaded every month to the site
These traffic and size numbers are nothing short of astonishing. He's accomplished all this on his own, using only five servers with the same Microsoft and ASP.NET stack we use. This gives me great hope for scaling Stack Overflow without needing a lot of employees or server hardware. I'm not sure we'll ever reach those kinds of traffic levels.
That said, there are some dark clouds on the horizon; in a recent blog post, Markus noted that their free business model doesn't always scale as well as the hardware:
The problem with free is that every time you double the size of your database the cost of maintaining the site grows 6 fold. I really underestimated how much resources it would take, I have one database table now that exceeds 3 billion records. The bigger you get as a free site the less money you make per visit and the more it costs to service a visit.
Of course, any resemblance between a free dating site and a question-and-answer site for programmers is purely coincidental, I'm sure.
In the early years of programming, a program was regarded as the private property of the programmer. One would no more think of reading a colleague's program unbidden than of picking up a love letter and reading it. This is essentially what a program was, a love letter from the programmer to the hardware, full of the intimate details known only to partners in an affair. Consequently, programs became larded with the pet names and verbal shorthand so popular with lovers who live in the blissful abstraction that assumes that theirs is the only existence in the universe. Such programs are unintelligible to those outside the partnership.
Maybe Stack Overflow is also built on love, internet style. Here's hoping that scales as well as Plenty of Fish has.
Update: Markus notes that according to hitwise, as of 2008, he runs the #13 website in the United States.
Idea counts, dev't is the issue of Developers, not of users. People would still go for a DOS based app if you give 'em what they need!
Don't worry. SO has started good. We are all lookin' forward to its massive success.
Saj on December 11, 2008 10:56 AMHow is Stack Overflow doing? I see it's up to 50,000+ questions. How many users? How many hits? Are you seeing any issues with scaling?
I haven't noticed any performance related issues. My biggest problem with the site is the signal-to-noise ratio seems to be falling due to the sheer volume of questions and answers. I wish there were more ways to sort and analyze the questions to help me find what I'm looking for faster.
Kuerwen on December 11, 2008 10:58 AMat first i thought it's about the image rescaling issue, which is something PoF.com clearly needs to work on as well...
anon on December 11, 2008 11:18 AMSigh. Another poor domain name choice (a la expertsexchange) -- I read that one as "plenty offish".
Chris C. on December 11, 2008 11:26 AMYes. Back in the good old days, the programmer was much more of a tyrant. He had absolute control over everything.
Now, with the advent of - open source libraries, internet, web services, write once run everywhere languages, external data sources, dynamic loading of code even in statically typed languages - you write a program of 1000 lines which is nothing more than the tip of a 100,000 lines ice-berg. The other parts were written by other guys, who will maintain them, change them, sometime remove them, without consulting you.
Programming is now much closer to democracy (some may say, anarchy). By the people. For the people.
Hmmm, www.okcupid.com is about 10x better in every way, and is also completely free. Plenty STILL stretches uploaded user images into squares making its thumbnails useless. Plus, the people on it are generally, to be frank, trashier than those on OKCupid.
sp160n on December 11, 2008 11:47 AMIt's amazing what you can do without that much hardware. And this is even truer for a free service that doesn't need to be up 99.99...% of the time.
But even so, you have to give credit where credit is due. Markus really knows what he's doing. To be able to handle that kind of traffic by yourself, well it's legendary!
Steph on December 11, 2008 11:50 AMHey Now Jeff,
StackOverflow will scale & it's a credit to ASP.NET.
Coding Horror Fan,
Catto
Catto on December 11, 2008 12:19 PMAlright! thanks for the link. Now to loggon and get laid! Yeeeeha!
John A. Davis on December 11, 2008 12:21 PMBe careful when you say "uses ASP.NET". Part of why he was able to run so much on one server was that he didn't use web forms, server controls, etc. Raw string concat (this is according to an interview he gave on Channel9).
Kevin Dente on December 11, 2008 12:23 PMBTW, Markus was my answer to the Stack Overflow "who is your programming hero".
Kevin Dente on December 11, 2008 12:23 PMWell if Microsoft reads this they should donate him some resources in exchange for the advertising he's already doing them. Putting these numbers on a fact sheet for ASP.NET wins the competition hands down.
Jason on December 11, 2008 1:18 PMThere is a wicked article about how he scaled at:
http://highscalability.com/plentyoffish-architecture
But it is definitely not a credit to asp.net, he used none of their controls. We are doing the same with the web app we are building, we use all the ado.net, .net xml classes and the rest of the framework except asp.net controls. We found the controls generated WAY too much html for our complex UIs. We do use http handlers and some webservices for our ajax stuff.
Quan on December 11, 2008 1:23 PMHe's got some of the worst HTML soups ever: mixed case, tables and bad javascript... yeah i'm envious of his success! ;-)
EnvyCoder on December 11, 2008 1:25 PMWow, it is great to see others, starting a web site, and making loads of income from it. Mostly, unexpectedly.
Also, this is just a testiment to the power of the word FREE, has on people.
Sure you can goto match.com or eharmony.com or millionairematch.com and PAID, but it goes to show, that a BASIC site design, with little to no CSS site design or fansy business front, is needed.
I myself run very successfull advertising sites, using the power of FREE.
Matt Kukowski on December 11, 2008 1:45 PMI love this kind of post because sometimes is very hard to find information of this type with real numbers. I don't want to debate about other technologies here or what/who is better, but I would love to hear/read about other combination of OS + Web Framework + DB with real numbers, any link/references posted here would be awesome.
mauricio quiros on December 11, 2008 1:59 PM3 <I>billion</i> rows?
Do I want to know what that's a table <I>of</I>?
Sigivald on December 11, 2008 1:59 PMHis table with 3 billion rows, actually flows into a much larger observation.
I've seen this in every company I've worked for. Subprime mortgages, healthcare, insurance, finance, etc. You start an app and it works great. With each passing month you have more data in your database. Eventually you have 1 million records and you start looking at indexing, then it's 5 million and you start looking at upgrading hardware. Then you have 50 million and you start fine tuning queries and such.
The longer you stay in business, the more it costs you to handle the transactions. Now presumably during this same time period, you're also automating other things and building economies of scale. This whole time the database is growing, we're talking about how can we archive off stuff, but nobody really wants to take responsibility for that answer.
It's like there is a natural progression where the older a company gets the more inefficient it becomes, and this allows for a competitive advantage to a young startup.
That is, unless you do something about this problem.
And it's not just data, it's a lot of stuff that you collect over time as a company. Could be boxes of paper. Could be a fleet of airplanes. Just interesting.
Steve Sheldon on December 11, 2008 2:35 PM> Part of why he was able to run so much on one server was that he didn't use web forms, server controls, etc. Raw string concat
Isn't that pretty much how ASP.NET MVC works? It's certainly one of the reasons I chose it.. just get the heck out of my way!
Jeff Atwood on December 11, 2008 2:36 PMSo he's got 16 CPUs for the app servers and they are doing 500-600 hits a second. ie 37.5 requests a second. That is about right really.
Take a pretty normal Ruby on rails application and a single CPU will do about the same. Of course scaling it so linearly so easily is the key here but even so its not uber, its about right. Now if we were seeing 70 hits/sec then this would be about twice as fast as most sites can do and that would be special.
Paul Keeble on December 11, 2008 3:03 PMJeff give us some simillar statistics regarding StackOverflow.com please :)
Andrei Rinea on December 11, 2008 4:36 PM>Isn't that pretty much how ASP.NET MVC works?
MVC is a lot closer to that than Web Forms. But it still goes through the rendering pipeline, has master pages and user controls, route resolution, parameter binding, ... Markus' version is just about as close to the metal as ASP.NET can get.
Kevin Dente on December 11, 2008 5:17 PMI have to admit, I always look forward to Catto's comments.
Love ya Catty
slapnuts on December 11, 2008 6:36 PM
More interesting than the scaling strategy (of which there are plenty of descriptions already on sites like highscalability.com) is the Plenty of Fish owner's position that "free does not scale". he makes some very interesting arguments; it would be a lot more interesting to have Jeff's take on *that* !
(edit: ... rather than a passing reference to that argument; this is a really contentious issue, and the contrarian position is poorly explored)
Louis-Eric on December 11, 2008 7:05 PMHere's an interview and tour with Frind from his Vancouver host Peer1:
http://www.peer1.com/aboutus/customer_stories_plentyoffish.php
Fred on December 11, 2008 7:09 PM@Paul Keeble, You have any high-scalability stats or links to back that rails claim up? I'm not a rails-hater, but last I heard rails wasn't 'linearly scalable' and nobody pretends it is.
It appears most of POF's high availability tricks are applicable to any language. All it's doing is reducing framework overhead. When you add generic frameworks (web forms, rails, mvc) you're making it easier and less buggy to program against, but you also make it slower overall. For most websites this is okay because you just chuck a little more hardware at it and the problem goes away.
This isn't the case for high-traffic websites, which is the whole point of the blog post.
Anyways it just goes to show you that how the program works (any program) is more important than how slick it looks. I'm also impressed that this is just 1 guy working away.
What I'd also like to know are the economies involved. The revenue from ads is high, and 2 servers aren't that expensive, but what is the bandwidth bill like?
someguy on December 11, 2008 8:18 PM"to be frank, trashier than those on OKCupid."
You say that like it's a bad thing ;)
Matt on December 12, 2008 1:53 AM@Paul Keeble, someguy:
Rails is not scalable - the database abstraction will kill a site sooner or later. Twitter is a case in point (ironically used more often by RoR advocates missing the point). It was scaled primarily with a massive amount of caching, which, of course, bypasses almost all of Rails' clunky whirring & grinding.
Schmoo on December 12, 2008 2:49 AMYou shouldn't be surprised that fish scales ;)
dan on December 12, 2008 3:09 AMActually considering the hardware, I don't see this as a scaling wonder. The hardest work is probably performed by the database servers and we have no information what giant performance beasts these are.
Handling 64000 simul. connections can be achieved with much worse hardware. Each of his servers has 8 cores (2 CPUs Quad Core) and he has two of them. That 16 cores, each 2.66 GHz, can handle 64000 is not really surprising. These are 8000 connections per core and that is doable with 2.66 GHz.
If I profile our web servers, I see that Apache is actually only 20% of the work-load (and that includes the PHP scripts running in Apache) and 80% of the time is taken by MySQL performing database operations. So if we offload the database to an external server, we have 80% CPU time spare. Ok, I must admit that we pay a lot of attention to make sure that MySQL does the actual work wherever possible. PHP doesn't do much more than building the SQL statement, firing it to the database and put some HTML formating around the results.
We made sure that all heavy work-load is performed by MySQL (since if you can do something in PHP or directly in SQL, you can bet that SQL will do it faster than you ever could do it in PHP). And now that MySQL has Subselects, you can run even much more complicated requests within a single SQL statement instead of fetching data from the database in PHP and then build more SQL statements based on this data. Thus whenver our server slows down and check where the load comes from, usually always the database is the culprit.
Somehow we developers just can't convince the management that we must stop running the backend database on the same servers as the web frontend... they don't want to listen to us. We could probably once buy a set of really huge performance beasts to run the SQL backend and easily replace our web frontend servers with much weaker, more lightweight machines.
Mecki on December 12, 2008 3:27 AM3 billion records, sounds like a script needs to be run through every so often to clear out old data, its probably message posts or something if it's that large. Just archive it off, improve speed even more.
pete on December 12, 2008 3:33 AM> Part of why he was able to run so much on one server was that he didn't use web forms, server controls, etc. Raw string concat
Does anyone use the asp.net webforms/controls?
I find them extremely annoying but i use asp anyway because i love the .net framework. I only use the asp:literal or asp:placeholder to put the generated content on the page.
Not to ben an a**hole or anything, but I don't find the design of SO that much better then that of plentyoffish. It's a little better, but it better should because you guys hired a real designer for it, right?
alvin on December 12, 2008 5:06 AMWhen you compare PlentyofFish with MySpace, it makes you ask the question:
What the hell are MySpace doing will all those extra servers?
Stephen Hill on December 12, 2008 5:41 AM@Mecki: Ok, I must admit that we pay a lot of attention to make sure that MySQL does the actual work wherever possible. PHP doesn't do much more than building the SQL statement, firing it to the database and put some HTML formating around the results.
Refreshing to know that a youngster (you are, yes?) gets what databases are good for. Not that MySql is spiffy for a transactional application.
BuggyFunBunny on December 12, 2008 6:04 AM2x database = 6x maintenance?
do you really need a database in that instance?
(might a filesystem suffice?)
Jeff, does your wife know that you're spending so much time on PlentyOfFish?
Kris on December 12, 2008 6:44 AMASP.NET controls are great for prototyping and rapid development. If you need to throw a site together and don't want to start mucking around with HTML, javascript, and input checking you can't do worse than what's available. But it's probably not a great idea to make that prototype into your main site without a lot of optimization. When I was getting started I never understood why some sites would use println after println. It made it difficult to update and maintain those pages. It became apparent why not too long after (though I still hated to maintain pages with hardcoded html).
Also, after updating so many customer databases it really becomes a nightmare to keep a database running. Sometimes it would be easier to just flush the entire thing and start fresh but they have years of information stored on those systems. You learn to tiptoe around the problems and learn the importance of transactions.
Joe Chin on December 12, 2008 7:02 AMScaling issues are always the fault of some programmer who made a tool or library that you use which is not intended to be scalable.
So, in reality it's always your fault :)
Practicality on December 12, 2008 7:35 AM"The problem with free is that every time you double the size of your database the cost of maintaining the site grows 6 fold. I really underestimated how much resources it would take, I have one database table now that exceeds 3 billion records. The bigger you get as a free site the less money you make per visit and the more it costs to service a visit."
I'm not sure what to make of this. I've never run an ad supported website so maybe I'm wrong but I thought that advertisers paid more money if their ads were exposed to more people. So higher traffic should mean more cash from advertisers right?
o.s. on December 12, 2008 8:14 AM@sp160n: Hmmm, www.okcupid.com is about 10x better in every way, and is also completely free.
# 1.2 billion page views per month, 500,000 average unique logins per day
# 30+ million hits per day, 500-600 per second
# 45 million visitors per month
# top 30 site in the US, top 10 in Canada, top 30 in the UK
It doesn't matter. I think that's the point of Jeff's post.
Greg H on December 12, 2008 8:30 AMIf you haven't known, check this out.
[duplicate of 2nd link in article]
he's the no.1 adsense user in Canada, making 10million a year, which is way more enough to pay off his bandwidth bill. :)
Kent on December 12, 2008 9:45 AMI disagree with the last quote. There were definitely hacker communities in the early days of programming (see Richard Stallman's book Free Software, Free Culture for examples) that encouraged sharing of code to a great degree. Heck, Stallman even started GNU following frustration from being unable to debug a proprietary printer driver, which was pretty much the only proprietary thing in the entire AI Media Lab, operating systems included.
Cyde Weys on December 12, 2008 9:53 AMAnother thing to point out is that he is serving all those images through a CDN (Akamai). While very expensive, they do remove the load, space, and bandwidth from your servers
Rich on December 12, 2008 10:00 AMFrom highscalability blog: "IIS arbitrarily limits the total connections to 64,000 so a load balancer was added to handle the large number of simultaneous connections"
WHAT?!?! And people actually pay for that?!?!
"No caching functionality in ASP.NET is used. It is not used because as soon as the data is put in the cache it's already expired."
I'm thinking this is an example of "doing it wrong".
James on December 12, 2008 10:46 AMThere are so many ways/technologies/techniques for building websites it's staggering ... least to me it is.
It's funny because the very first asp.net app I ever wrote simply had a server tag for returning the page generated server side. I thought it was totally hack at the time, but maybe not so much?
Then later on when I had to build some sites for a customer (and this is without, really any other experience) I used the ASP.NET server controls and whatnot for user entry and all. I really didn't have any time (as I was the sole dev) to learn some of the MVC/jquery-AJAXy style stuff ... and while the site works and is pretty solid, I read articles like this (and some of these comments) and just go "Damn, 101 ways to skin a cat indeed..."
Mal on December 12, 2008 11:12 AMScalability worries me quite a bit. Very soon, me and two co-workers will be developing a web app (using C#/ASP.NET) and have very little experience in doing so as efficiently as possible.
I'm not sure our idea will directly get anyone laid, so it might be doomed to failure.
Charles Callebs on December 12, 2008 11:29 AM@Mecki "We made sure that all heavy work-load is performed by MySQL"
I'd have thought that you reach a point where you can only scale a database so far (i.e. better hardware), whereas if there is more logic in the web-layer, you can keep adding more servers to the web-farm to handle that load.
If you've got one shared server available (sounds like you do?) the MySQL heavy load seems fair - just wondering how you'd approach it if you had more servers available, and where you'd place the heavy lifting then?
Starburn on December 12, 2008 1:51 PMDid you mention he makes around half a million dollars a month in adsense from the site? The limited hardware could also be done in the linux world by simply avoiding apache and using other far better (free/commercial) replacements. But it's the adsense that blows me away at $10 million in income per year.
_ck_ on December 14, 2008 3:31 AMThis is very comforting as I am planning to scale my website which also runs on asp.net mvc. It is a hosted microblog platform and it is still in private beta and less than 2 weeks old and I already have 200+ sites created. My problems will be less than stack overflow because this is a paid service, so the growth will be limited. If it was free like twitter then I would run into those kinds of problems very quickly. The site I am referring to is www.yonkly.com
BTW, I am using Amazon EC2 hosting, so I can quickly provision new servers and do DNS round robin if there is a huge surge in traffic. Scaling the database would be another problem. But being on EC2 is very comforting.
Emad Ibrahim on December 14, 2008 10:12 PM
I'm still doing everything myself except for customer service.
Current numbers are.
60-65 Million Pageviews per day, 4.4 million per hour peak.
72 million visitors a month
3 load balanced Windows Server 2003 x64 web servers with 2 Quad Core CPU sits at about 20% cpu at peak, 2 Quads... Makes it easy for me to take servers up and down without worrying about crashing.
Sites running on 5 DB's now, between 64 and 128 GB of ram, Got a huge 30% increase in traffic coming on Dec 26th same as every year. Every page on the site has a bar on images on it... To create that bar a radius search is done along that uses your history as well as preferences. Its not possible to cache anything as its true personalization and each query depends on the previous one. Same with all the searches.
Over 130,000 Concurrent users at peak.
500M images per day.
Asp.net for the most part is irrelevant when it comes to scaling, because it uses so little resources. I use StringBuilder, Response.Write and access the DB. C# is the last thing I think about when it comes to scaling issues, its 99% the DB.
Jeff -
In the 1970's many of my colleagues would not run a program unless they had read the source code and compiled it themselves. Those who wanted to share their work put the source on open display - it certainly was not like your love letter metaphor.
-Lepto
@Starburn: A database won't scale beyond a certain point, but where is the difference of throwing better hardware at it compared to running more web servers? In both cases you must buy hardware. The only difference is that in one case you *replace* hardware, in the other case you *add* hardware. However, no matter how many webservers you run, if they all share the same data, you'll need a central database again and this will sooner or later always become your weak link.
@BuggyFunBunny: Youngster :-) Well, I'm slowly starting to group out of this term. At least my cards don't say "Junior Software Developer" anymore, just "Software Developer". Lets see how many years to go before I'm a Senior. And all I know about LAMP I learned from the best (unfortunately one of them already left the company). When I started, my first project was a grown, old, web-based document management system. The task was: Make it run faster. This was the first time I was doing something meaningful with PHP and the first time I really had to understand SQL Selects in all their beauty. By limiting the amount of SQL statements (2 statements per page viewed instead of 31 statements per page, still with the same data in return) I was able to speed up the system dramatically. From that day on I really studied SQL statements to find out how much more work you can actually already do in the database, since it is also much nicer for a programmer to just create a statement of how the result should look like instead of getting a huge blob of information and having to manually "write code to get it into the desired state".
Mecki on December 19, 2008 8:09 AMI think the simplicity desgin of Plentyoffish, gives users a feeling of trust, and belonging. After all, most of us (singles) are living in a messy room. When it comes to websites deals with personal matters and life, I much prefer the low key, causal design of Plentyoffish, just a sense of belonging.
Ross Lin.
Ross Lin on December 23, 2008 11:58 AMi'm not sure if it's been said, and it definitely doesn't belong on this blog (except that maybe you care, since you said a few things about security).
plentyoffish has the WORST security in the history of the internet. not only does it (have to) have a completely unencrypted database of the passwords of every user, it sends em out WITH EVERY SINGLE EMAIL IN PLAIN TEXT.
why would anyone want their password sent to them every single month ? i do not know.
if one was in the habit of using the same password for everything he signed up for on the internet (not a stretch of imagination here) he could not read his email with someone standing behind him, ever.
ok the rant is over.
>> The problem with free is that every time you double the size of your database the cost of maintaining the site grows 6 fold.
that is a point to remember. and i think that's a point advertising companies should take into consideration. the problem with this is .... you hardly ever get negative growth. so eventually you will have to charge people for using your site since the ad revenues don't cover the cost anymore. which would be bad for everyone involved, the advertising company (or the sites you're advertising for) yourself, and the users.
Alexander Knopf on December 23, 2008 8:59 PMJeff,
I'd like to start a free budget/personal finance site and will need plenty of horsepower and storage. I'm definitely a nubee, so how does one get started in terms of hardware infrastructure? Do I need to get a dedicated IP from my ISP and obtain my own servers? Do I go with amazon or Sql Server Data Services/Azure or something like that? Is the latter services free or a discount offering available to non-profit/free services such as the budget/personal finance site I'm looking to start?
markymark315 on December 29, 2008 7:19 AMEvery time I feel like I'm going numb and going into demotivational stage, I look up at Markus's work and refill my lunges with new energy.
Awesomeness!
Gil Megidish on January 15, 2009 2:40 PMDid you mention he makes around half a million dollars a month in adsense from the site? The limited hardware could also be done in the linux world by simply avoiding apache and using other far better (free/commercial) replacements. But it's the adsense that blows me away at $10 million in income per year.
http://sadushki.ru/
Its too bad Marcus wont share more information to help others with their web development and programming quest. I know many have helped him along the way, I am not sure why he would not want to return the favor. I would think he could at least tell someone new where to start their learning, how to optimize code, what technologies he thinks works best and what areas they should do research for the future how to figure it out for themselves how to get a high traffic automated web system up for their online ideas. Example
1.) Asp.net - Learn these functions of it, don't use this part of it and optimize your code by doing this (Study this other technology that I am thinking about changing it to for this reason possibly? Future plans?)Tips on automation and optimization. Should we think about C# or other future Microsoft technologies?
2.) Web Servers - Recommended Hardware, Windows 2003 64bit, this hardware, this setup and configuration and use it this way
3.) SQL 2005 (Or whatever) - Recommended Hardware, Windows 2003 64bit, What version, how setup, tips on utilization, use this way for reads and use this way for writes, how to optimize for high traffic, Etc.
4.) Bandwidth and other network optimizations?
5.) Good resources you used online to help you figure stuff out??
6.) Any other helpful tips on AI and other stuff you use?
You are rich now! This is one way you can share your wealth in knowledge without having to spend a cent. Just give us enough to figure out the detailed creation ourselves?
Or create a framework we can buy or something. Just help a brotha out!
Bless us oh Marcus our Friend! :-)
Share the Wealth on February 11, 2009 12:41 AMI think the simplicity desgin of Plentyoffish, gives users a feeling of trust, and belonging. After all, most of us (singles) are living in a messy room. When it comes to websites deals with personal matters and life, I much prefer the low key, causal design of Plentyoffish, just a sense of belonging.
http://touravus.ru
I think Mr. Frind will not share or discuss his secret..The reason it's business.
american girls on July 1, 2009 11:32 PM| Content (c) 2009 Jeff Atwood. Logo image used with permission of the author. (c) 1993 Steven C. McConnell. All Rights Reserved. |