Forum Moderators: coopster
Obviously ping and the basics would be fairly simple but i'm also looking for unique ideas i can use in the script for running tests on the host? I can't run a script on the host's to test its performance so what other alternative things could i possibly do?
I was thinking of using apache response codes ( or perhaps this is what ping already uses?) and somehow sending a huge request to the server which would generate 1000's of response codes and timing this and using a benchmark to get a rough idea of performance and other figures such as comparing it to ping speed to get an idea of processing power and speed?
I was thinking of using 404 pages for tests but they can vary from server to server.
I'm just guessing at this stage but really looking for some ideas on how to go about this (how i could measure performance in some way from a remote host) Much appreciate and feedback or ideas.
thanks heaps, by the way free script to anybody who gives me useful info or help hehe
Obviously this idea has its own problems as in far as some index pages are dynmaic and rewritten to .html so processing engines for those will interfere with a reliable figure. Perhaps using an image from the index page? ( not so good for index pages which have no image or graphic)
I'd say take a step back, and perhaps come up with ten measurables that you know will work. Instead of trial and error, maybe a more structured approach could help?
- GD (create large images)
- Large mysql query
- Read/parse large file (same on all servers)
- Traceroute
- Recursion (try executing function until overloads :) )
etc