Benefits & Features
(Why you should just move to FastNet2 over FastNet or others?)
Easy to Use (Not complex & Documentation available)
- Better Optimization & Performance
Stability & Efficient (reduced throttling & efficiently handling heavy multi-events)
One-remote for All (less overhead and reduce cost for multi-events usage)
Multi-Threads Re-uses (with advanced multi-threading)
Safety check (prevent internal errors with few extra check)
Identifier Serialization (reduce identifier event byte cost)
- Lightweight but very-fast
Memory-leaks prevention (reduces memory usage to prevent memory-leak happens)
FastNet2 version: rc9 (0.9.3)
FastNet2 is currently on development, and FastNet2 is not ready for use/producted
Test Benchmark (Result)
Note: These Benchmark is at 500 packets sent every 0.5s, test in Studio
FastNet2 (default settings, rateLimit 500, v0.9.3/rc9)
FastNet2 (default settings, rateLimit off, v0.0.8-preAlpha-refresh)
BridgeNet2 (default settings, v0.5.2)
Red2 (default, rc11)
What you currently using?
- Native (Roblox Remote)
- FastNet (v1/v2)
- BridgeNet (v1/v2)
- Red (v1/v2)
- Self Custom Library
- Other Library
Will you use FastNet2 in the future?
- Yes i’m
- No, but maybe later?
- Good enough overall
- Still needs more improvement/updates
how is this any better than BridgeNet? any comparisons?
you can download the “Networking Test” rbxm file i uploaded and also dont forget to update the fastnet2 source on it, the v0.0.2 available now
So basically FastNet2’s job is to make the player have lower bandwidths on Wi-Fi and decrease avg ping?
If you had any idea/suggestions/feedbacks, let met know.
screenshots of the benchmarking place file for anyone that’s too lazy 2 download the place themselves
i removed the FastNet from benchmark (reason: FastNet had big problem on queue, when it not firing the queue still push until the queue stores is empty so it may break others when benchmarking)
also fastnet2 is now v0.0.3
It’s funny how you released FastNet2 for no particular reason when BridgeNet2 is also in the works. It just offers all the features that BridgeNet has but it’s just a copy. Not saying it’s bad to recreate stuff, but looking through the code it looks similar, and you released FastNet2 for no reason.
hot fix on client side (.rbxm, not published on github & wally, will be released when next update)
what did you mean i didnt copy and following how BridgeNet2 ecosystem works and i even dont understand how bridgenet2 system inside, all i do is doing experiments
Why is your code exactly like BridgeNet2’s code?
I also found another thing similar
??? its package of wally config, and im using rojo if you have made wally and rojo package you prob know
im not stealing their idea im just learned from all/common signals module (not network)
Well, then I am deeply sorry if I have caused you any trouble, have a good day .
updated benchmark file to newest [included with hot fix upd]
bro does not know what wally.toml is
its not code, its more of a config. ofcourse their identical
You are trying to push the narrative that code was copied, even thought the only thing you showed was code that is a required config file…