|
Post by AnthroHeart on Mar 22, 2024 21:57:07 GMT
Do you think I should add a Mbit/s indicator?
|
|
|
Post by reden on Mar 22, 2024 22:06:26 GMT
Do you think I should add a Mbit/s indicator? I don't think it's needed
|
|
|
Post by nathanmyersc on Mar 22, 2024 23:18:03 GMT
I updated to v0.14 to fix a few bugs.
Before it was getting to Q (Quintillions) fast but that wasn't accurate as it was only Trillions of repetitions after the similar amount of time.
Had to fix the formatting. Also made the output look better if there's an error, which will eventually work itself out. Still will have to test this.
Also using strings now to hold really large numbers. The code that the developer used for string number adding on the Intention Repeater really helped.
If I don't use multithreading and don't use multiplying the internet still works, but is slower. Use Multithreading and Multiplying when you're not using the internet.
Enter your Intention: I am Love. MultiThreaded (y/N): y Use Multiplying (y/N): y Use Hashing (y/N): y Broadcasting: [00:00:17] 4.617T Repetitions (357.340GHz) Shutting down... Enter your Intention: I am Love. MultiThreaded (y/N): n Use Multiplying (y/N): y Use Hashing (y/N): y Broadcasting: [00:00:03] 494.779B Repetitions (137.438GHz) Shutting down...
Not sure how much help it is but your still not setting the sockets buffer size. // Set socket buffer size
int bufferSize = 2048 * 2048; // Example buffer size (4MB), you can adjust as needed
if (setsockopt(socks[i], SOL_SOCKET, SO_SNDBUF, (const char*)&bufferSize, sizeof(bufferSize)) == SOCKET_ERROR) {
std::cerr << "Error in setting UDP buffer size with error: " << WSAGetLastError() << std::endl;
closesocket(socks[i]);
WSACleanup();
return 1;
}
|
|
|
Post by AnthroHeart on Mar 23, 2024 0:00:41 GMT
Thanks. I made the update and it's about 1000X faster now.
I'll give it some more tests before posting an update.
Running at 100PHz equivalent using multithreadding, multiplying and hashing. Up from 220GHz.
|
|
|
Post by AnthroHeart on Mar 23, 2024 1:08:17 GMT
Ok, I updated to v0.14 which runs much faster. I am using a UDP Socket now, and require intention to be specified.
With just "x" as an intention I'm getting 1EHz equivalent with hashing, multithreading and multiplying.
Enter your Intention: x MultiThreaded (y/N): y Use Multiplying (y/N): y Use Hashing (y/N): y Broadcasting: [00:00:24] 24.729Q Repetitions (1.006EHz) Shutting down...
Binary: github.com/tsweet77/intention-repeater-wifi/raw/main/Intention_Repeater_WiFi.exe
Code: github.com/tsweet77/intention-repeater-wifi/raw/main/Intention_Repeater_WiFi.cpp
Required: github.com/tsweet77/intention-repeater-wifi/raw/main/picosha2.h
|
|
|
Post by nathanmyersc on Mar 23, 2024 1:27:00 GMT
Ok, I updated to v0.14 which runs much faster. I am using a UDP Socket now, and require intention to be specified. With just "x" as an intention I'm getting 1EHz equivalent with hashing, multithreading and multiplying. Enter your Intention: x MultiThreaded (y/N): y Use Multiplying (y/N): y Use Hashing (y/N): y Broadcasting: [00:00:24] 24.729Q Repetitions (1.006EHz) Shutting down... Binary: github.com/tsweet77/intention-repeater-wifi/raw/main/Intention_Repeater_WiFi.exe Code: github.com/tsweet77/intention-repeater-wifi/raw/main/Intention_Repeater_WiFi.cpp Required: github.com/tsweet77/intention-repeater-wifi/raw/main/picosha2.h awesome im totally always going to sleep playing it. or when im absent from the computer. and write my intention like Nathan Myerscough recieves the following benefits : I AM GODLIKE NOW. WITH GODLIKE PHYSIQUE AND REGENERATIVE CAPABILITIES.
|
|
|
Post by AnthroHeart on Mar 23, 2024 1:29:42 GMT
Are you making modifications for your own use? I notice in your example you use socks instead of threadsocks.
|
|
|
Post by nathanmyersc on Mar 23, 2024 1:38:30 GMT
Are you making modifications for your own use? I notice in your example you use socks instead of threadsocks NOT atm. been tired i might have a look at some point. was just providing all the wisdom i could for you to make the best version. id use yours at this point. but if i come up with any ideas il let you know.
|
|
|
Post by reden on Mar 23, 2024 4:16:16 GMT
Ok, I updated to v0.14 which runs much faster. I am using a UDP Socket now, and require intention to be specified. With just "x" as an intention I'm getting 1EHz equivalent with hashing, multithreading and multiplying. Enter your Intention: x MultiThreaded (y/N): y Use Multiplying (y/N): y Use Hashing (y/N): y Broadcasting: [00:00:24] 24.729Q Repetitions (1.006EHz) Shutting down... Binary: github.com/tsweet77/intention-repeater-wifi/raw/main/Intention_Repeater_WiFi.exe Code: github.com/tsweet77/intention-repeater-wifi/raw/main/Intention_Repeater_WiFi.cpp Required: github.com/tsweet77/intention-repeater-wifi/raw/main/picosha2.h I wonder if Repeater C++ were multithreaded, it would be as fast as this.
|
|
|
Post by nathanmyersc on Mar 23, 2024 4:52:39 GMT
Ok, I updated to v0.14 which runs much faster. I am using a UDP Socket now, and require intention to be specified. With just "x" as an intention I'm getting 1EHz equivalent with hashing, multithreading and multiplying. Enter your Intention: x MultiThreaded (y/N): y Use Multiplying (y/N): y Use Hashing (y/N): y Broadcasting: [00:00:24] 24.729Q Repetitions (1.006EHz) Shutting down... Binary: github.com/tsweet77/intention-repeater-wifi/raw/main/Intention_Repeater_WiFi.exe Code: github.com/tsweet77/intention-repeater-wifi/raw/main/Intention_Repeater_WiFi.cpp Required: github.com/tsweet77/intention-repeater-wifi/raw/main/picosha2.h I wonder if Repeater C++ were multithreaded, it would be as fast as this. Id imagine that if we did multiplying and hashing with multithreading it would be faster than sending it via wifi. but maybe not i figure writing a variable is less costly than sending data through a socket. But totally multithreading makes the code much faster. i made my own multithreaded versions for text files and image files and intents. But not including hashing or multiplication of intent. That would definitely boost it. i figure hashing is no different than what we are doing with wav files. we are selecting the noise arbitrarily basically. The noise itself has little connection to the words. But effects are observable regardless. So a hash of a multiplid intention or image or text file could be very powerful. i ponder a hash of a 10000kb text file that has about 100,000 unique affirmations in it. cause i got quite a few text files like that for various things.
|
|
|
Post by nathanmyersc on Mar 23, 2024 5:08:05 GMT
Are you making modifications for your own use? I notice in your example you use socks instead of threadsocks. I had another thought, perhaps the PORT is also a bottle neck so perhaps choosing a unique port for every thread could speed things up a bit. Also since the main thread only does something once per second you could also be transmitting on the main thread until the 1 second interval. more sped that way. although its going to use like your entire CPU Heres your code with those modifications its faster. also consider not having spaces between your words can increase the speed as well.
Attachments:main.cpp (14.43 KB)
|
|
|
Post by AnthroHeart on Mar 23, 2024 14:31:29 GMT
Are you making modifications for your own use? I notice in your example you use socks instead of threadsocks. I had another thought, perhaps the PORT is also a bottle neck so perhaps choosing a unique port for every thread could speed things up a bit. Also since the main thread only does something once per second you could also be transmitting on the main thread until the 1 second interval. more sped that way. although its going to use like your entire CPU Heres your code with those modifications its faster. also consider not having spaces between your words can increase the speed as well.
I didn't notice a difference in the speed between the two.
I can see about removing spaces.
|
|
|
Post by reden on Mar 23, 2024 14:34:57 GMT
I wonder if Repeater C++ were multithreaded, it would be as fast as this. Id imagine that if we did multiplying and hashing with multithreading it would be faster than sending it via wifi. but maybe not i figure writing a variable is less costly than sending data through a socket. But totally multithreading makes the code much faster. i made my own multithreaded versions for text files and image files and intents. But not including hashing or multiplication of intent. That would definitely boost it. i figure hashing is no different than what we are doing with wav files. we are selecting the noise arbitrarily basically. The noise itself has little connection to the words. But effects are observable regardless. So a hash of a multiplid intention or image or text file could be very powerful. i ponder a hash of a 10000kb text file that has about 100,000 unique affirmations in it. cause i got quite a few text files like that for various things. Yet this is the implementation that achieves 1 EHz (1 sextillion) from one letter Intention, which is beginning to get up there with CUDA. When I said Repeater C++, I meant Repeater MAX C++. The comparative lack of speed in it is probably due to the lack of multithreading. >i ponder a hash of a 10000kb text file that has about 100,000 unique affirmations in it. cause i got quite a few text files like that for various things. I did something similar, as I explained in another thread. 1000 text files with 1 million Intentions each, except for the last that had 10 million, packed up in a tar, that was later xz'd (super compressed) to get a file smaller than 1 MB. Then the hash was computed, and the next sequence was made, with all the files containing the hash of the previous as the sole Intention. The very first file of the set contained INTENTIONS.TXT So when you repeated the fifth, say, the universe seeked through them as a laser, powering the intentions up, and tuning them to the heart chakra for some reason. When I tried using 5 (5 million intentions per file, etc) instead of 10, the latter effect did not appear.
|
|
|
Post by AnthroHeart on Mar 23, 2024 14:56:15 GMT
Are you making modifications for your own use? I notice in your example you use socks instead of threadsocks. I had another thought, perhaps the PORT is also a bottle neck so perhaps choosing a unique port for every thread could speed things up a bit. Also since the main thread only does something once per second you could also be transmitting on the main thread until the 1 second interval. more sped that way. although its going to use like your entire CPU Heres your code with those modifications its faster. also consider not having spaces between your words can increase the speed as well.
I incorporated your code, and added option for removing spaces. It didn't make much of a difference in the regular speed. I didn't feel like adding the repeating into the main thread. I think it's doing that anyway for non-multithreaded.
|
|
|
Post by nathanmyersc on Mar 23, 2024 17:31:27 GMT
I had another thought, perhaps the PORT is also a bottle neck so perhaps choosing a unique port for every thread could speed things up a bit. Also since the main thread only does something once per second you could also be transmitting on the main thread until the 1 second interval. more sped that way. although its going to use like your entire CPU Heres your code with those modifications its faster. also consider not having spaces between your words can increase the speed as well.
I didn't notice a difference in the speed between the two.
I can see about removing spaces.
Removing spaces would increase speed, as well as having the main thread sending packets when its doing nothing. If the main thread is also sending packets between its 1 second of displaying interval it increases speed. This program uses my entire cpu hahaha.
|
|