I need to benchmark apache website in linux server.
I have configured Siege and it works fine..
When I run siege on local host I get transaction rate ie 625.00 trans/sec
command is : siege -b -c 200 -r 10 http://localhost
When I run same siege on different site I get different transaction rate i.e 99.21 trans/sec
siege -b -c 200 -r 10 http://apache.org
I want to know how my Apache server is being used in siege when I run for different sites.
please clarify this.
The website in your local host is by naturally faster than the ones hosted live. The server response time will be very fast in the local server.
Related
I need some help with a really strange problem.
I use wget (busybox) to obtain the the IP address of some remote clients, to use it on a DNS (a sort of "homemade ddns"). Those clients run a script that every 5 mins calls
wget -O /dev/null "https://my_dns.org/poll.php?user=User_N&pwd=password_N"
Everything was fine, until I updated my http server to remove TLS1.0/TLS1.1
After updating: running the above command on the clients' console it still works OK, while running it automatically (launching it from a script in /etc/init.d) I get this error:
Connecting to my_dns.org (www.xxx.yyy.zzz:443)
wget: error getting response: Connection reset by peer
...Any idea about why does this happen, and how to fix...?
(The shell on the clients runs as root...)
Thank you in advance for your help
Regards
I have one machine with postgres client libraries (machine_C) and one machine with postgres server (machine_S)
When I run pg_dump from the machine with postgres client and use the -h option with the server IP. Who is actually doing the hard work. Is it the server machine (machine_S) or the client machine (machine_C).
In addition, is it better to run this command locally on the server machine and copy the file or to use the -h option and to write it directly on the client machine
Thanks
In the light of your comment above, the correct answer is to run it on the client machine:
The work that the database has to do is the same.
The amount of data transferred is roughly the same.
You save the time and I/O capacity of first writing and then reading the dump file on the server machine.
There is a small trade-off if you are using pg_dump -Fc with compression – dumping on the server will hog the server machine's CPU, but the amount of data transferred over the network will be less. Consider doing that if your network is particularly lame, otherwise just run it on the client machine.
As pythonanywhere is the one of best place to host python web app. And apps will be hosted as per wsgi.py configurations on it's own server. But what happens when I do something like this on its bash shell?
$ python manage.py runserver 127.0.0.1:9000
Performing system checks...
System check identified no issues (0 silenced).
April 28, 2016 - 15:29:48
Django version 1.9.5, using settings 'MyProject.settings'
Starting development server at http://127.0.0.1:9000/
Quit the server with CONTROL-C.
As you can see I had changed the port to :9000, so is there any way to access this or it's just meaningless as it's serving the app on served server service?
PythonAnywhere dev here. There's no way to access a server you run using manage.py runserver. It will try to bind to a local port, but that port isn't visible from outside the PythonAnywhere cluster.
[edit] Oh, and thank you for the kind words about PythonAnywhere!
I have 3 servers all running repcached (memcached patch to support replication)
Is there a way that I can invalidate the whole cache on all servers at once?
Right now, I first stop all servers and then start them one by one
Thanks
send this command to the server,
echo "flush_all" | nc 127.0.0.1 11211
my memcached server have to be "flush_all" per about 12 hours ,unless the app would down soon.
if i ignore some memcached settings? my app based on java/tomcat
i startup memcached by typed "nohup ./memcached -p [port] -m 8192" that all,
i' can't found the configure file of my memcached server.
i installing memcached by typed tar zxf memcached-version.tar.gz
cd memcached-version/
./configure -prefix /usr
make && make install
How much memory do you have on that machine? if you have 8G, what might be happening is that memcached is taking up all the memory available on the machine.
if so, just change the memcached startupline to -m 5000 or so.