Yes give me one sec and ill get it and edit this message with it included
Netty module:
Netty.rbxm (16.2 KB)
Yes give me one sec and ill get it and edit this message with it included
Netty module:
Netty.rbxm (16.2 KB)
Yes, it’s called request you can check the documentation for more info
Ok
type or paste code here
It failed to do anything when I was trying to test
Benchmark (2).rbxl (256.4 KB)
Check if I have set netty up correctly, and if not can you send me a fixed place
Ok i will check if you implemented it right
If you plan to send large data multiple times a frame and aren’t worried about receiving it instantly and are more concerned with network usage then disable the firing of the events per heartbeat and just when the batch fills up this allows for more complex and large data to be sent in a single event saving a lot of network usage and aren’t worried about small increase in latency
You can also adjust the size of the maxflushbatch inside Dynamic Sender to suit your needs, it will become remote event dependant and a configurable option in the future
Edit Constants Module for more refined tuning etc
GitHub and Roblox have been both updated!
Thank you to
@weakroblox35 - spotting queue issue
I have a problem when i try registering a remote event from a client script (not the RegisterRequestEvent)
17:46:48.062 Players.zak_isla.PlayerGui.controller.Chat.chatscript:10: attempt to call missing method 'RegisterEvent' of table
i dont know if its my fault for me using it incorrectly or it doesnt support client → server firing at all
:RegisterEvent()
is a Server only function, for client use :GetEvent()
wich gets the event you Registered on the server already
oh ok thanks
type or paste code here
@TheYusufGamer Forgot that netty doesnt support sending tables. You might have to redo the benchmarks to not send tables over but rather singular arguments. Also here is the properly implemented netty, even though it doesnt rlly work as it doesnt support sending tables.
BenchmarkNew.rbxl (257.4 KB)
You forgot to update GitHub code to version 1.1.1
Yeah I updated releases not the soure code just yet, I will in a few min
Edit: Updated changed scripts on github repo
Have you got any thoughts on this?
I have no bad intentions, but if a table cannot even be sent, why are we benchmarking it?
I can’t really test it if its not possible to send arrays, but I can just test by sending a repeating string? if you want just try
local data = string.rep("A", 8000) -- Whatever you whant
and Use it within a task.wait()
loop
Also you should change Register event to GetEvent as it’s server only.
local reportLatencyEvent = NetRay:RegisterEvent(!)
Thanks for pointing that out, I’ll update the documentation soon
Im talking about netty only. You can remove netty for now until you change the way the modules are benchmarked.
You’re missing a 5 second delay between the tests to allow the network to return to baseline and task.wait(1 / amount)
I don’t remeber if that was there originally for the loop
otherwise it looks good
You are free to modify and fix any issues that you stumble upon