Linux/PHP vs. ASP
We are about to start a project which will enable users to query a
database and which will return results and record their queries. The
table being queried on will have about 10,000 records, and each query
will write one record to another table (we expect to eventually get
200-500 queries a day, so that table would eventually have in the
neighborhood of 100,000 records. We are trying to decide what
configuration to use, and have narrowed it down to Linux/PHP/MySQL vs
ASP/MSSQL. Any opinions? Should we be concerned about the lack of
scalability of MySQL?
Also is there a difference in performance between Linux/PHP and ASP?
We're just getting started, so any info/tips
would be greatly appreciated.
mairving posted this at 20:16 — 5th February 2003.
They have: 2,256 posts
Joined: Feb 2001
Scalability shouldn't be any problem at all at that level. I am not a big fan of ASP/M$SQL since I feel like PHP/MySQL runs much faster on similar machines. Certainly PHP/MySQL would save you some money also. Here are some reasons to go with PHP. I will let Peter give you the reasons to go with ASP.
Mark Irving
I have a mind like a steel trap; it is rusty and illegal in 47 states
zollet posted this at 22:23 — 5th February 2003.
He has: 1,016 posts
Joined: May 2002
I HIGHLY recommend you going with PHP/MySQL mainly for the reasons given in the link provided above.
listless posted this at 17:56 — 6th February 2003.
They have: 11 posts
Joined: Jan 2003
Similar Q on DevShed
Seven reasons why PHP is better
Benchmark results from MySQL.com (well, de in this case)
For a project as small in scope as what you mention, I see no real advantage to using Microsoft stuff, unless you have a pre-existing investment in their gear. Too much dough, insufficient support. My dos pennies.
This is my band. || This is me.
Wil posted this at 17:07 — 7th February 2003.
They have: 601 posts
Joined: Nov 2001
Why not go for postgresql? It's a much better database than MySQL in terms of stability and it's SQL dialect.
mairving posted this at 17:34 — 7th February 2003.
They have: 2,256 posts
Joined: Feb 2001
I would disagree with that. I have never had nor seen a stability issue with MySQL. Plus it is much easier to find scripts, hosts, etc for MySQL.
Mark Irving
I have a mind like a steel trap; it is rusty and illegal in 47 states
listless posted this at 17:43 — 7th February 2003.
They have: 11 posts
Joined: Jan 2003
MySQL trounces Postgresql in all the benchmark tests I've seen, tho I'll admit having only seen a few.
Mark Hensler posted this at 18:36 — 7th February 2003.
He has: 4,048 posts
Joined: Aug 2000
I've not worked with postgre at all, but I've been told it does support stored proceedures and triggers. Something that you'll have to wait for in mySQL version 4 (it is in there, right?).
Mark Hensler
If there is no answer on Google, then there is no question.
mairving posted this at 20:48 — 7th February 2003.
They have: 2,256 posts
Joined: Feb 2001
4.0 has been in Alpha forever. It has finally made it to Gamma. Beta can't be far behind.
Mark Irving
I have a mind like a steel trap; it is rusty and illegal in 47 states
Mark Hensler posted this at 23:08 — 7th February 2003.
He has: 4,048 posts
Joined: Aug 2000
But will 4.0 have stored procs & triggers?
Wil posted this at 12:56 — 8th February 2003.
They have: 601 posts
Joined: Nov 2001
I'm not sure Mark, I do hope so. Postgresql does indeed have the one up on MySQL over a number of features in 3.x MySQL. I think version 4 will be a huge step forward for MySQL and a welcomed one at that.
Same story with Apache 2/mod_perl 2 though. It's a waiting game. But until the wait is over, I'll continue to use postgresql, especially on high traffic sites where there's a lot of interaction with the database in terms of adding/updting records.
MySQL is super fast for *retrieving* records from the database. Anything more than that and it falls down big time from my own experience.
- wil
Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.