Record me compiling siege on macOS

by Devin Yang
(This article was automatically translated.)

Published - 7 years ago ( Updated - 7 years ago )

Siege is an http load testing and benchmarking tool. Used to stress test the code.
Siege supports basic authentication, cookies, HTTP, HTTPS and FTP protocols.
It allows users to access web servers by simulating concurrent connections etc.

If automake is not installed in the OSX system, please download and install it from Gnu FTP first. The version I use in this article is version 1.16.

http://ftp.gnu.org/gnu/automake/

In the automake directory, the compilation method is very simple

./configure
make
make install

First of all, of course, you must download the Source Code from github.

git clone https://github.com/JoeDog/siege

Enter the directory, execute the following instructions, compile and install

utils/bootstrap
./configure
make
make install

The command is as follows:

siege -d10 -c10 -i -f urls.txt

The file of urls.txt can be as follows:

http://example.test/
http://example.test/path1
http://example.test/path2

-d10 is delay
-c10 is the number of simultaneous connections
-i Simulate the user randomly clicking on the URL
-f selects the specified URL

Tags:

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

Synology,siri

Turn on synology nas with Siri

I have two Synology NAS at home. One of the Nas for backup is usually turned off. I’m not sure if turning it on and off every day will hurt the machine, but I’m sure if it’s not turned off for 24 hours, it will hurt the hard drive. The hard drive for business is about 5~ It will be replaced in 6 years, and this Nas is usually used for nothing and consumes power. Therefore, at this stage, I only let it automatically turn on at a fixed time to receive backup data.

php

Apache removed the Authorization Header issue

Apache removed the Authorization Header, no solution can be seen in $_SERVER.

laravel, livewire

livewire important notes

Before starting your Livewire journey, here are three basic considerations about public properties: 1. The property name must not conflict with a property name reserved for Livewire (such as $rules or $message) 2. Store in Data in public properties is visible to front-end JavaScript. Therefore, you should not store sensitive data in it. 3. Properties can only be JavaScript-friendly data types (string, integer, array, boolean), or one of the following PHP types: Stringable, Collection, DateTime, Model, EloquentCollection.