|
|
Post by AnthroHeart on Mar 24, 2024 0:25:50 GMT
I ran typeperf in Windows to see how many bytes/sec I was transferring. These are the first 20 seconds of running the WiFi Broadcaster.
To see your interfaces: typeperf -qx "\Network Interface"
To record bytes per second: typeperf "\Network Interface<name of interface>\Bytes Sent/sec" -o C:\path\to\file\Typeperf.csv
My example: typeperf "\Network Interface(Intel[R] Wi-Fi 6 AX201 160MHz)\Bytes Sent/sec" -o C:\Repeater\WiFi\WiFi_Typeperf.csv
I wonder why it was only transferring 1,906 bytes per second, unless I am reading that wrong. I chose "y" for everything.
1 [ 1906.37166701041 ]
2 [ 1393.15468301328 ]
3 [ 1422.48131097464 ]
4 [ 1440.42377564474 ]
5 [ 1946.10206129747 ]
6 [ 998.635000690524 ]
7 [ 571.129765820986 ]
8 [ 405.072735749615 ]
9 [ 175.034779509578 ]
10 [ 365.609716793547 ]
11 [ 955.235996304703 ]
12 [ 841.34080520785 ]
13 [ 526.410312100956 ]
14 [ 267.117587536412 ]
15 [ 394.828440115955 ]
16 [ 527.08184001704 ]
17 [ 497.540045296916 ]
|
|
|
|
Post by nathanmyersc on Mar 24, 2024 0:36:43 GMT
I ran typeperf in Windows to see how many bytes/sec I was transferring. These are the first 20 seconds of running the WiFi Broadcaster.
To see your interfaces: typeperf -qx "\Network Interface"
To record bytes per second: typeperf "\Network Interface<name of interface>\Bytes Sent/sec" -o C:\path\to\file\Typeperf.csv
My example: typeperf "\Network Interface(Intel[R] Wi-Fi 6 AX201 160MHz)\Bytes Sent/sec" -o C:\Repeater\WiFi\WiFi_Typeperf.csv
I wonder why it was only transferring 1,906 bytes per second, unless I am reading that wrong. I chose "y" for everything.
1 [ 1906.37166701041 ]
2 [ 1393.15468301328 ]
3 [ 1422.48131097464 ]
4 [ 1440.42377564474 ]
5 [ 1946.10206129747 ]
6 [ 998.635000690524 ]
7 [ 571.129765820986 ]
8 [ 405.072735749615 ]
9 [ 175.034779509578 ]
10 [ 365.609716793547 ]
11 [ 955.235996304703 ]
12 [ 841.34080520785 ]
13 [ 526.410312100956 ]
14 [ 267.117587536412 ]
15 [ 394.828440115955 ]
16 [ 527.08184001704 ]
17 [ 497.540045296916 ]
Try only sending in chunks closer to MTU and see if that improves anything. Broadcasting to noone in general is kind of esoteric in nature anyways. Yes, sending packets that are too large can potentially slow down the transfer rate. This is because of a mechanism called "packet fragmentation." When data is transmitted over a network, it is divided into smaller units called packets. Each packet has a maximum size limit, which is determined by the Maximum Transmission Unit (MTU) of the network. If a packet exceeds the MTU of a particular network segment, it needs to be fragmented into smaller packets that fit within the MTU. Fragmentation adds overhead to the transmission process because it requires additional processing by both the sending and receiving devices. Sending larger packets that require fragmentation can increase the likelihood of delays, packet loss, and retransmissions, especially in scenarios with high network congestion or devices with limited processing capabilities. Therefore, it's generally advisable to optimize packet sizes to fit within the MTU of the network to minimize fragmentation and improve overall transfer rates. i think that when we send a command to our interface it doesnt wait for the command to be finished. It just sends the command and returns. so perhaps try sending close to Maximum transmission unit and see if that changes anything. |
|
|
|
Post by AnthroHeart on Mar 24, 2024 0:44:46 GMT
If my MTU is 1500, should I go a bit smaller than that for overhead?
|
|
|
|
Post by AnthroHeart on Mar 24, 2024 1:05:58 GMT
Ok, I did it with a value of 1460 for packet size, and got these results in bytes/sec. A bit better, but it was with multithreading. I may try without that and see.
21955.8836259473
1527.81594597173
2167.68785215635
1015.80533641689
597.400173690398
1880.64744528241
3913.38519627105
231.859404420568
54.647680936236
185.137498253817
593.600667686788
534.020248547435
657.911098573809
0
175.03156006915
3945.75605206319
|
|
|
|
Post by AnthroHeart on Mar 24, 2024 1:07:35 GMT
Without multithreading I get these bytes/sec transfers with 1460 buffer size.
442.484227219115
1654.92150069436
126.729122342414
54.4661446367286
367.374200329845
22261.512951472
689.858553188938
228.853740961144
2733.19058137583
174.953239545877
0
514.601699276286
178.205770837477
449.2856655458
426.598062571741
466.786967545719
|
|
|
|
Post by nathanmyersc on Mar 24, 2024 1:13:00 GMT
my version works i stopped all internet processes and this is my type of output due to the progrma "03/23/2024 18:09:12.931","200374.12366497720359" "03/23/2024 18:09:13.946","6659501.1952908914536" "03/23/2024 18:09:14.961","4672984.11473691836" "03/23/2024 18:09:15.975","2992655.9043659372255" "03/23/2024 18:09:16.990","4028423.8253168258816" "03/23/2024 18:09:18.005","3146402.9436284122057" "03/23/2024 18:09:19.020","6232166.5543143535033" "03/23/2024 18:09:20.035","5777040.7092412430793" "03/23/2024 18:09:21.049","7259196.527292705141" "03/23/2024 18:09:22.064","6572264.5578026100993" "03/23/2024 18:09:23.078","7545455.2807309534401" "03/23/2024 18:09:24.092","6921844.7644290411845" "03/23/2024 18:09:25.107","9760591.0063100382686" "03/23/2024 18:09:26.122","9476371.8700289521366" "03/23/2024 18:09:27.137","8431140.1697460748255" "03/23/2024 18:09:28.152","5887363.5066227978095" "03/23/2024 18:09:29.166","8036804.6591748585925" "03/23/2024 18:09:30.181","9771462.9536089170724" "03/23/2024 18:09:31.196","8588709.0535487569869" "03/23/2024 18:09:32.211","8559227.1610567867756" mine is transmitting between 2 and 8 megabytes per second. "03/23/2024 18:09:33.226","6434147.7604633513838" i didnt even change the packet size to the MTU. not sure whats different between our stuff. maybe your firewall is blocking the program idk. Attachments:main.cpp (20.09 KB)
|
|
|
|
Post by nathanmyersc on Mar 24, 2024 1:16:28 GMT
"03/23/2024 18:13:01.309"," "
"03/23/2024 18:13:02.324","0"
"03/23/2024 18:13:03.339","0"
"03/23/2024 18:13:04.354","0"
"03/23/2024 18:13:05.369","0"
"03/23/2024 18:13:06.383","92470.03789458416577"
"03/23/2024 18:13:07.398","5945804.1019157608971"
"03/23/2024 18:13:08.413","11053416.332930987701"
"03/23/2024 18:13:09.428","7849124.0569144990295"
"03/23/2024 18:13:10.443","11782280.885402917862"
"03/23/2024 18:13:11.457","12705185.395400810987"
"03/23/2024 18:13:12.472","11146277.843372318894"
"03/23/2024 18:13:13.487","7626322.5415819231421"
"03/23/2024 18:13:14.502","10614329.826352465898"
"03/23/2024 18:13:15.517","9362490.7755131628364"
"03/23/2024 18:13:16.531","11256752.500864202157"
"03/23/2024 18:13:17.546","11088625.501676697284"
"03/23/2024 18:13:18.561","11798936.16297964938"
"03/23/2024 18:13:19.576","7430171.820242526941"
"03/23/2024 18:13:20.591","6244727.4347609048709"
"03/23/2024 18:13:21.606","8215993.6319201784208"
"03/23/2024 18:13:22.620","8420982.0972381141037"
"03/23/2024 18:13:23.635","8863343.9652630724013"
"03/23/2024 18:13:24.650","13146793.971730787307"
"03/23/2024 18:13:25.665","11841421.954669322819"
|
|
|
|
Post by AnthroHeart on Mar 24, 2024 1:26:01 GMT
Interesting. I ran your code and got these results. But I didn't stop internet processes, but I wasn't using the internet either while running.
I chose 0 threads, 1GB of RAM.
03/23/2024 20:23:42.788 2889.4791320821
03/23/2024 20:23:43.799 5247.35480488131
03/23/2024 20:23:44.807 1750.64517182885
03/23/2024 20:23:45.828 858.123429851834
03/23/2024 20:23:46.842 2317.21019335733
03/23/2024 20:23:47.852 983.436278875194
03/23/2024 20:23:48.876 359.420945509538
03/23/2024 20:23:49.901 719.050696976719
03/23/2024 20:23:50.926 1393.44819783139
03/23/2024 20:23:51.950 1478.44255104042
03/23/2024 20:23:52.973 1063.79202944044
03/23/2024 20:23:53.983 980.909093878543
03/23/2024 20:23:55.012 903.390066034994
03/23/2024 20:23:56.036 839.52335378256
03/23/2024 20:23:57.246 835.595474593435
03/23/2024 20:23:58.257 531.261735739926
03/23/2024 20:23:59.267 251.421820088089
03/23/2024 20:24:00.276 1600.64826750391
03/23/2024 20:24:01.283 14305.9242895484
|
|
|
|
Post by AnthroHeart on Mar 24, 2024 1:27:19 GMT
Weird. I get this when I'm not even running the WiFi broadcaster. I wonder if I have the right interface.
03/23/2024 20:26:38.658 0
03/23/2024 20:26:39.682 172.929988952021
03/23/2024 20:26:40.704 5891.83567596957
03/23/2024 20:26:41.729 970.232126572149
03/23/2024 20:26:42.737 1290.63721566796
03/23/2024 20:26:43.758 1540.86965624786
03/23/2024 20:26:44.772 1553.33915153361
|
|
|
|
Post by nathanmyersc on Mar 24, 2024 1:37:49 GMT
Weird. I get this when I'm not even running the WiFi broadcaster. I wonder if I have the right interface. 03/23/2024 20:26:38.658 0 03/23/2024 20:26:39.682 172.929988952021 03/23/2024 20:26:40.704 5891.83567596957 03/23/2024 20:26:41.729 970.232126572149 03/23/2024 20:26:42.737 1290.63721566796 03/23/2024 20:26:43.758 1540.86965624786 03/23/2024 20:26:44.772 1553.33915153361 I cleaned up the code a bit heres a better version.You might not be looking at the right interface or you are blockign it with your firewall idk EDIT i had to make another modification. EDIT2 i had to make another modification again. EDIT3 i made another modification just cleaning up the code. Attachments:main.cpp (20.09 KB)
|
|
|
|
Post by reden on Mar 24, 2024 2:40:50 GMT
I ran typeperf in Windows to see how many bytes/sec I was transferring. These are the first 20 seconds of running the WiFi Broadcaster.
To see your interfaces: typeperf -qx "\Network Interface"
To record bytes per second: typeperf "\Network Interface<name of interface>\Bytes Sent/sec" -o C:\path\to\file\Typeperf.csv
My example: typeperf "\Network Interface(Intel[R] Wi-Fi 6 AX201 160MHz)\Bytes Sent/sec" -o C:\Repeater\WiFi\WiFi_Typeperf.csv
I wonder why it was only transferring 1,906 bytes per second, unless I am reading that wrong. I chose "y" for everything.
1 [ 1906.37166701041 ]
2 [ 1393.15468301328 ]
3 [ 1422.48131097464 ]
4 [ 1440.42377564474 ]
5 [ 1946.10206129747 ]
6 [ 998.635000690524 ]
7 [ 571.129765820986 ]
8 [ 405.072735749615 ]
9 [ 175.034779509578 ]
10 [ 365.609716793547 ]
11 [ 955.235996304703 ]
12 [ 841.34080520785 ]
13 [ 526.410312100956 ]
14 [ 267.117587536412 ]
15 [ 394.828440115955 ]
16 [ 527.08184001704 ]
17 [ 497.540045296916 ]
Try only sending in chunks closer to MTU and see if that improves anything. Broadcasting to noone in general is kind of esoteric in nature anyways. Yes, sending packets that are too large can potentially slow down the transfer rate. This is because of a mechanism called "packet fragmentation." When data is transmitted over a network, it is divided into smaller units called packets. Each packet has a maximum size limit, which is determined by the Maximum Transmission Unit (MTU) of the network. If a packet exceeds the MTU of a particular network segment, it needs to be fragmented into smaller packets that fit within the MTU. Fragmentation adds overhead to the transmission process because it requires additional processing by both the sending and receiving devices. Sending larger packets that require fragmentation can increase the likelihood of delays, packet loss, and retransmissions, especially in scenarios with high network congestion or devices with limited processing capabilities. Therefore, it's generally advisable to optimize packet sizes to fit within the MTU of the network to minimize fragmentation and improve overall transfer rates. i think that when we send a command to our interface it doesnt wait for the command to be finished. It just sends the command and returns. so perhaps try sending close to Maximum transmission unit and see if that changes anything. >Broadcasting to noone in general If it's the broadcast address, isn't it to all devices within a network? So if you did this while on mobile data, it might send to the cell tower, and therefore affect everyone on range. |
|
|
|
Post by AnthroHeart on Mar 24, 2024 2:43:11 GMT
I did the command: typeperf "Network Interface(*)\Bytes Total/sec" Which should monitor all network traffic. It jumps around a little randomly when the WiFi broadcaster isn't running. But when I am running the WiFi Broadcaster, the typeperf doesn't jump up in number. So I tried using all network interfaces, but it still isn't picking it up.
I tried nathan's code too and it was the same.
|
|
|
|
Post by nathanmyersc on Mar 24, 2024 2:50:22 GMT
I did the command: typeperf "Network Interface(*)\Bytes Total/sec" Which should monitor all network traffic. It jumps around a little randomly when the WiFi broadcaster isn't running. But when I am running the WiFi Broadcaster, the typeperf doesn't jump up in number. So I tried using all network interfaces, but it still isn't picking it up. M previous version was retarded try this. Try turning off firewall maybe idk Attachments:main.cpp (20.09 KB)
|
|
|
|
Post by AnthroHeart on Mar 24, 2024 2:54:25 GMT
I did the command: typeperf "Network Interface(*)\Bytes Total/sec" Which should monitor all network traffic. It jumps around a little randomly when the WiFi broadcaster isn't running. But when I am running the WiFi Broadcaster, the typeperf doesn't jump up in number. So I tried using all network interfaces, but it still isn't picking it up. M previous version was retarded try this. Try turning off firewall maybe idk I turned off my firewall, and ran your latest code, but it still didn't show a spike in total network usage.
Maybe on my computer it isn't Network Interface. I don't know.
|
|
|
|
Post by nathanmyersc on Mar 24, 2024 3:11:50 GMT
M previous version was retarded try this. Try turning off firewall maybe idk I turned off my firewall, and ran your latest code, but it still didn't show a spike in total network usage.
Maybe on my computer it isn't Network Interface. I don't know.
Hmm that is strange for me its consistent. I just realized i sent you the wrong program. HAHAHAH that was my intention repeater. Attachments:main.cpp (16.62 KB)
|
|
