By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,751 Members | 1,175 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,751 IT Pros & Developers. It's quick & easy.

MySQL Load with PHP

P: n/a
Would a medium sized (~500 pages) database driven website, search
engine and mailing list be too much for one MySQL database? Instead of
making using different databases I would use different tables. I would
use PHP for all of this.

Any help would be greatly appreciated.
Jul 17 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
Peter Bach wrote:
Would a medium sized (~500 pages) database driven website, search
engine and mailing list be too much for one MySQL database? Instead of
making using different databases I would use different tables. I would
use PHP for all of this.

Any help would be greatly appreciated.


that will depend on the OS and hardware involved and the number of
anticipated hits. for maybe a few hundred hits a week it might not be
too bad, but if your talking many hits per minute, then you might want
to use something better. MySQL was designed to used in small-ish
environments, but some people seem to push whatever technology to the
edge of the envelope. Try to ensure that your database "doesn't
matter". And by that I mean that you will be able to move it to a more
enterprise-class database engine if need be (I currently do not consider
SQL Server to be "Enterprise" class, although there are those who would
disagree with me :)....

Michael Austin
DBA (Oracle and OracleRdb - formerly DEC Rdb on OpenVMS).
Jul 17 '05 #2

P: n/a
Peter Bach wrote:
Would a medium sized (~500 pages) database driven website, search
engine and mailing list be too much for one MySQL database? Instead of
making using different databases I would use different tables. I would
use PHP for all of this.

Any help would be greatly appreciated.


Not according to the mysql documentation, it wouldn't: 'Handles large
databases. We use MySQL Server with databases that contain 50 million
records. We also know of users who use MySQL Server with 60,000 tables
and about 5,000,000,000 rows.'

HTH,
Margaret
--
(To mail me, please change .not.invalid to .net, first.
Apologies for the inconvenience.)
Jul 17 '05 #3

P: n/a
In message <qp********************************@4ax.com>, Margaret
MacDonald <sc**********@att.not.invalid> writes
Peter Bach wrote:
Would a medium sized (~500 pages) database driven website, search
engine and mailing list be too much for one MySQL database? Instead of
making using different databases I would use different tables. I would
use PHP for all of this.

Any help would be greatly appreciated.
Not according to the mysql documentation, it wouldn't: 'Handles large
databases. We use MySQL Server with databases that contain 50 million
records. We also know of users who use MySQL Server with 60,000 tables
and about 5,000,000,000 rows.'


Not much help without knowing what the load is, IMHO.

HTH,
Margaret


--
Five Cats
Email to: cats_spam at uk2 dot net
Jul 17 '05 #4

P: n/a

"Five Cats" <ca*******@[127.0.0.1]> wrote in message
news:bQ**************@[127.0.0.1]...
In message <qp********************************@4ax.com>, Margaret
MacDonald <sc**********@att.not.invalid> writes
Peter Bach wrote:
Would a medium sized (~500 pages) database driven website, search
engine and mailing list be too much for one MySQL database? Instead of
making using different databases I would use different tables. I would
use PHP for all of this.

Any help would be greatly appreciated.


Not according to the mysql documentation, it wouldn't: 'Handles large
databases. We use MySQL Server with databases that contain 50 million
records. We also know of users who use MySQL Server with 60,000 tables
and about 5,000,000,000 rows.'


Not much help without knowing what the load is, IMHO.

HTH,
Margaret


The OP hasn't even mentioned the rate of potential hits, just the size of
the data. To which the answer is "yes, easily". Access speed is a function
of hardware, table design and the ability of the database drivers to handle
multiple concurrent requests. Any shortcoming of those three will drop you
in it; I don't believe MySQL will be the weak link.

Chances are, if the OP is asking about design questions on Usenet, s/he's
not going to be in charge of a project where hit rate is going to be an
issue. No offence. 8)

Garp
Jul 17 '05 #5

P: n/a
I use Intel servers with Dual Xeon processors and Linux/Red Hat &
Apache. A "few hundred hits a week" is probably all I'll get. But
traffic may increase...

Michael Austin <ma*****@firstdbasource.com> wrote in message news:<Pn*****************@newssvr22.news.prodigy.c om>...
Peter Bach wrote:
Would a medium sized (~500 pages) database driven website, search
engine and mailing list be too much for one MySQL database? Instead of
making using different databases I would use different tables. I would
use PHP for all of this.

Any help would be greatly appreciated.


that will depend on the OS and hardware involved and the number of
anticipated hits. for maybe a few hundred hits a week it might not be
too bad, but if your talking many hits per minute, then you might want
to use something better. MySQL was designed to used in small-ish
environments, but some people seem to push whatever technology to the
edge of the envelope. Try to ensure that your database "doesn't
matter". And by that I mean that you will be able to move it to a more
enterprise-class database engine if need be (I currently do not consider
SQL Server to be "Enterprise" class, although there are those who would
disagree with me :)....

Michael Austin
DBA (Oracle and OracleRdb - formerly DEC Rdb on OpenVMS).

Jul 17 '05 #6

P: n/a
"Garp" <ga***@no7.blueyonder.co.uk> wrote in message
news:MX*********************@news-text.cableinet.net...
The OP hasn't even mentioned the rate of potential hits, just the size of
the data. To which the answer is "yes, easily". Access speed is a function
of hardware, table design and the ability of the database drivers to handle multiple concurrent requests. Any shortcoming of those three will drop you
in it; I don't believe MySQL will be the weak link.


Not that having multiple databases would have any material affect on server
load. We are still dealing with the same amount of data regardless of how
you divide it up.
Jul 17 '05 #7

P: n/a
MySQL will quite easily handle this. In any case this could be
considered over-kill. SQLite could even handle this.

Grant

Peter Bach wrote:
I use Intel servers with Dual Xeon processors and Linux/Red Hat &
Apache. A "few hundred hits a week" is probably all I'll get. But
traffic may increase...

Michael Austin <ma*****@firstdbasource.com> wrote in message news:<Pn*****************@newssvr22.news.prodigy.c om>...
Peter Bach wrote:

Would a medium sized (~500 pages) database driven website, search
engine and mailing list be too much for one MySQL database? Instead of
making using different databases I would use different tables. I would
use PHP for all of this.

Any help would be greatly appreciated.


that will depend on the OS and hardware involved and the number of
anticipated hits. for maybe a few hundred hits a week it might not be
too bad, but if your talking many hits per minute, then you might want
to use something better. MySQL was designed to used in small-ish
environments, but some people seem to push whatever technology to the
edge of the envelope. Try to ensure that your database "doesn't
matter". And by that I mean that you will be able to move it to a more
enterprise-class database engine if need be (I currently do not consider
SQL Server to be "Enterprise" class, although there are those who would
disagree with me :)....

Michael Austin
DBA (Oracle and OracleRdb - formerly DEC Rdb on OpenVMS).

Jul 17 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.