Have you also tried using the MicroProfiler to identify if there’s anything that’s a problem? I wouldn’t work off of these Shift + F[num] menus alone.
As for data, just double check what exactly you’re sending over the network. An array full of instances (lots of probably unused data)? An array full of strings (less data, but can be reduced)? An array full of integers (pretty good)? A single integer (the best)?
Typically when you need to worry about network overhead it’s a good idea for whatever arguments you need to be integers (or arrays/dictionaries that mostly contain integers). Advantages: simple, makes the network happy. Disadvantages: can make your code harder to read (there are ways around this, but I think that’s outside the scope of this post).
edit: my example of an array full of instances is actually wrong - instances can’t be sent over the network like this. Regardless, my point about keeping the data which is sent over the network compact is very important. Always prefer booleans or integers over strings; floating point numbers should only be used when they absolutely have to
Anyone have any further help with this? i found out what was messing with the KB/sec, and fixed it, but my network receive is still terrible. I don’t really like asking staff, but is there a good person to ping for this sort of issue?