Goatworks/RoadSign
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
🚦 路碑 | 一个不局限于反向代理的反向代理服务器
22 Commits 2 Branches 1 Tag 16 MiB
Go 54.8%
TypeScript 38.8%
HTML 3.5%
Python 1.9%
JavaScript 0.6%
Other 0.4%
f497ff6c6c
Go to file
LittleSheep f497ff6c6c
All checks were successful
release-nightly / build-docker (push) Successful in 1m9s
Details
🔀 Merge pull request '✨ One-liner 的 CLI' (#3) from features/cli into master 
Reviewed-on: https://code.smartsheep.studio/Goatworks/RoadSign/pulls/3
2023-12-10 06:54:26 +00:00
.fleet ✨ Credential of administration api 2023-11-25 00:34:51 +08:00
.gitea/workflows 💚 Fix CI workflow 2023-11-18 21:20:45 +08:00
.idea ✨ Transformers 2023-11-18 00:23:40 +08:00
.vscode ✨ Logger 2023-11-25 23:06:23 +08:00
config 🐛 Bug fixes 2023-11-25 23:56:55 +08:00
pkg ✨ CLI Deploy 2023-12-10 14:52:00 +08:00
test/benchmark ✨ CLI Deploy 2023-12-10 14:52:00 +08:00
Dockerfile 💚 Fix dockerfile 2023-12-10 11:54:28 +08:00
go.mod ✨ CLI Deploy 2023-12-10 14:52:00 +08:00
go.sum ✨ CLI Deploy 2023-12-10 14:52:00 +08:00
README.md ✨ Built-in PM 2023-12-10 11:30:31 +08:00
settings.yml 📝 Update benchmark 2023-11-30 22:35:46 +08:00

README.md

🚦 RoadSign

A blazing fast reverse proxy with a lot of shining features.

Features

  1. Reverse proxy
  2. Static file hosting
  3. Analytics and Metrics
  4. Integrate with CI/CD
  5. Webhook integration
  6. Web management panel
  7. Blazing fast ⚡

Deleted item means under construction, check out our roadmap!

How fast is it?

We use roadsign and nginx to host a same static file, and test them with go-wrk. Here's the result:

Software Total Requests Requests per Seconds Transfer per Seconds Avg Time Fastest Time Slowest Time Errors Count
Nginx 515749 4299.58 2.05MB 13.954846ms 0s (Cached) 410.6972ms 0
RoadSign 8905230 76626.70 30.98MB 783.016µs 28.542µs 46.773083ms 0
RoadSign w/ Prefork 4784308 40170.41 16.24MB 1.493636ms 34.291µs 8.727666ms 0

As result, roadsign undoubtedly is the fastest one.

It can be found that the prefork feature makes RoadSign more stable in concurrency. We can see this from the Slowest Time. At the same time, the Fastest Time is affected because reusing ports requires some extra steps to handle load balancing. Enable this feature at your own discretion depending on your use case.

More details can be found at benchmark's README.md