php/MySQL questions

Linc · Post by **Linc** » Mon Dec 04, 2006 5:25 pm

Question for you LAMP programmers here. How fast of a LAMP server do you think I would need to keep up with somewhere between 30 and 80 simple queries per second for 16 hours/day?

By the way, I started LAMP discussion board over at:
http://linc.homeunix.org:8080/board/ind ... board=10.0
for those of you interested. If you are not already a member, sorry about having to wait for registration, but I just got my first asshole today with the porno spam and closed down the immediate registration.

snarkout · Post by **snarkout** » Mon Dec 04, 2006 7:33 pm

A picture of a bunghole?

Linc · Post by **Linc** » Mon Dec 04, 2006 7:45 pm

Snarkout wrote:A picture of a bunghole?

I'll leave that one up to Dann. I am sure he can think of something....

Tsuroerusu · Post by **Tsuroerusu** » Mon Dec 04, 2006 7:47 pm

Linc wrote:
Snarkout wrote:A picture of a bunghole?
I'll leave that one up to Dann. I am sure he can think of something....

Get ready for the next-gen version of the hoagie guy story, some guy having is ass in a shower.

yeti · Post by **yeti** » Tue Dec 05, 2006 8:47 am

I'd hate to guess but consider your database schema and volume of data too - a fast database with a poorly designed schema/queries will affect performance significantly

also, dont forget to allow some extra overhead for system growth

snarkout · Post by **snarkout** » Tue Dec 05, 2006 9:20 am

yeti wrote:I'd hate to guess but consider your database schema and volume of data too - a fast database with a poorly designed schema/queries will affect performance significantly

also, dont forget to allow some extra overhead for system growth

*Some* room being the key word here. Don't get that quad xeon system which will be an outdated hotass powerhungry bitch hog in a year but you'll be saddled with for the next 6 or 8 because everyone remembers how spendy it was.

Linc · Post by **Linc** » Tue Dec 05, 2006 11:12 am

yeti wrote:I'd hate to guess but consider your database schema and volume of data too - a fast database with a poorly designed schema/queries will affect performance significantly

also, dont forget to allow some extra overhead for system growth

This will be running basically only 1 thing, a very small query. I am going to look through a table of maybe a hundred or so two-field-long records.

Basically, it's a Computer-Telephony-Integration back end program that looks at a database to see if there is a record with NNNN phone extension, and if there is, return the callerid and remove the record.

gordonmarkus · Post by **gordonmarkus** » Wed Dec 06, 2006 5:05 pm

Hi,

not sure if this helps, but here goes...

In a former life I was the IT manager for a couple of reasonable size call centres (about 50 seats each), and we used to run a proprietry CTI server (Avaya) on a windows NT box which basically does the exact same thing that you are doing. When a call comes in, the PBX sends a message to the CTI server to say which agent is getting the call, then the CTI server performs a lookup to see on which PC the agent is sat, so that the screen can be popped with the relevent info. Anyway....

We were using a P4 machine with 512Mb, and a regular IDE HD. We never had a problem with over utilisation or anything. Bearing in mind that you'll be able to fine tune your own query and schema, something of this spec would be more than adequate I would have thought.

-Gordon.