Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Results #1

Open
MOVZX opened this issue Oct 3, 2024 · 1 comment
Open

Results #1

MOVZX opened this issue Oct 3, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@MOVZX
Copy link

MOVZX commented Oct 3, 2024

Using zLib DEFLATE, almost 70% savings on data sent from Server->Client, and vice versa.

image

Scenario for just 1 Server->Client Event:

  • The server sends 12 x 7.7 KB (92.4 KB) of data simultaneously to all players every 1 minute
  • If there's 80 players, it would be 7.392 KB (7.4 MB)
  • In a day, it would be 10.644.480 KB (10.6 GB) of data sent to client

Plain:
12 * 7.7 = 92.4
92.4 * 80 = 73.920
73.920 * 60 * 24 = 10.6444.800 (10.6 GB)

Now, using zLib DEFLATE:
12 * 2.6 = 31.2
31.2 * 80 = 2.496
2496 * 60 * 24 = 3.594.240 (3.6 GB)

From 10.6 GB down to 3.6 GB is huuuuuge, and that's just for a single event/script... 🥇

@AndrewR3K
Copy link
Contributor

Great research! This has been on my mind since you brought it up. I have now implemented zLib directly into our utils and it has made our RPC and Net events very small/fast. 🚀 🔥

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants