|
Post by sound on Jun 26, 2022 2:15:26 GMT
|
|
|
Post by reden on Jun 26, 2022 2:47:53 GMT
Correction, it shows the last letter of the affirmation (since it is TXT in my case, it is "T"). Might be a graphical glitch of no relevance.
|
|
|
Post by sound on Jun 26, 2022 2:58:02 GMT
Sounds likely. It happened on Windows too. It does not concern me, just wanted to make sure.
An observation: it takes a lot longer to load the intention on Ubuntu than Windows. Like a lot. More than double the time! No worries for me; I'll keep the thing running 24/7.
Alright... it's 5 am. I better get some rest. Honestly, I am feeling kind of high. Might be something to do with my new Repeater script, because I certainly have not ingested any drugs.
|
|
|
Post by reden on Jun 26, 2022 3:31:35 GMT
Sounds likely. It happened on Windows too. It does not concern me, just wanted to make sure.
An observation: it takes a lot longer to load the intention on Ubuntu than Windows. Like a lot. More than double the time! No worries for me; I'll keep the thing running 24/7.
Alright... it's 5 am. I better get some rest. Honestly, I am feeling kind of high. Might be something to do with my new Repeater script, because I certainly have not ingested any drugs. "An observation: it takes a lot longer to load the intention on Ubuntu than Windows. Like a lot. More than double the time!" That may be due to a filesystem difference. Most Linuxes use ext4. I wonder if it's worth it to check through several Linux filesystems in search for one as fast, or faster, than NTFS (Windows'). Speaking of drugs, chemicals&related, the Repeater can induce the effects of any you can think of, and even alien, fantastical, etc. ones.
|
|
|
Post by AnthroHeart on Jun 26, 2022 11:03:43 GMT
I can look into it. Should be a simple fix. I need an extra space at the end during the resting period to cover over that last letter.
|
|
|
Post by AnthroHeart on Jun 26, 2022 11:17:56 GMT
AnthroHeart reden : when a high --imem parameter is used together with --restevery --restfor, a "T" is shown next to the affirmation during the resting phase. This does not occur when a low --imem parameter is used with rest. What might be the reason? I updated to v5.7 to fix this issue:
Give it a try as I couldn't test it with large imem.
|
|
|
Post by reden on Jun 26, 2022 14:37:11 GMT
Sounds likely. It happened on Windows too. It does not concern me, just wanted to make sure.
An observation: it takes a lot longer to load the intention on Ubuntu than Windows. Like a lot. More than double the time! No worries for me; I'll keep the thing running 24/7.
Alright... it's 5 am. I better get some rest. Honestly, I am feeling kind of high. Might be something to do with my new Repeater script, because I certainly have not ingested any drugs. "An observation: it takes a lot longer to load the intention on Ubuntu than Windows. Like a lot. More than double the time!" That may be due to a filesystem difference. Most Linuxes use ext4. I wonder if it's worth it to check through several Linux filesystems in search for one as fast, or faster, than NTFS (Windows'). Speaking of drugs, chemicals&related, the Repeater can induce the effects of any you can think of, and even alien, fantastical, etc. ones. Filesystem... what was I thinking about. Oh, that's regarding swap. Some articles describe ext4 as being many times faster than NTFS: one said it's 30 times faster than it while copying files. But may be slower in this one thing, something very few if any people have ever noticed. Maybe something about how memory is allocated. Linux has many "schedulers", which are patterns to structure memory allocation.... oh wait, they're for CPU usage. Hmmmm... Edit: it may be this en.wikipedia.org/wiki/Allocate-on-flush I am not sure if it can be disabled.
|
|
|
Post by sound on Jun 26, 2022 17:10:08 GMT
Thank you both for the answers and help and comments. I decided to make my swap-file 50 GB (I hardly ever use up disk space) of the SSD but to use 12 GB with the Repeater, for the sake of loading times as well as being in the same region that other users are, so that the energy reaches me in the same way it reaches everyone else. Although I love to experiment, I feel there are better ways to do so than to increase the memory parameter. So 12.0 GB has become my "golden number". I also started using the Nesting utility with a level of 100. I added reden 's "scripts" to the beginning and end of my INTENTIONS.TXT (the script with the mantras, perfect amount of phz and all that). My entire INTENTIONS.TXT is around 217 lines long now. I am experimenting with the best way to use rest phase. Right now it is running at --restevery 20 --restfor 20. I am not sensitive enough to draw any conclusions about this but since Anthro Heart had said it is stronger I take his word for that.
Also reden: not a single BSOD since Ubuntu.
|
|
|
Post by reden on Jun 26, 2022 17:16:54 GMT
Thank you both for the answers and help and comments. I decided to make my swap-file 50 GB (I hardly ever use up disk space) of the SSD but to use 12 GB with the Repeater, for the sake of loading times as well as being in the same region that other users are, so that the energy reaches me in the same way it reaches everyone else. Although I love to experiment, I feel there are better ways to do so than to increase the memory parameter. So 12.0 GB has become my "golden number". I also started using the Nesting utility with a level of 100. I added reden 's "scripts" to the beginning and end of my INTENTIONS.TXT (the script with the mantras, perfect amount of phz and all that). My entire INTENTIONS.TXT is around 217 lines long now. I am experimenting with the best way to use rest phase. Right now it is running at --restevery 20 --restfor 20. I am not sensitive enough to draw any conclusions about this but since Anthro Heart had said it is stronger I take his word for that.
Also reden: not a single BSOD since Ubuntu. "... loading times as well as being in the same region that other users are, so that the energy reaches me in the same way it reaches everyone else." This is a bizarre perspective. Even with --imem 100, it would reach you the same way, as Repeater uses the same method to transfer the energy. The thing that changes is the size of the "gate", which allows more energy to pour out at once. Repeater's energy is effectively limitless and infinite. But how much of it pours out at a time is seemingly limited by the Repeat speed. It being faster helps to give every Intention more energy from the available bandwidth. Have you experimented with having 2 Repeaters running on the same file?
|
|
|
Post by sound on Jun 26, 2022 17:26:35 GMT
Thank you both for the answers and help and comments. I decided to make my swap-file 50 GB (I hardly ever use up disk space) of the SSD but to use 12 GB with the Repeater, for the sake of loading times as well as being in the same region that other users are, so that the energy reaches me in the same way it reaches everyone else. Although I love to experiment, I feel there are better ways to do so than to increase the memory parameter. So 12.0 GB has become my "golden number". I also started using the Nesting utility with a level of 100. I added reden 's "scripts" to the beginning and end of my INTENTIONS.TXT (the script with the mantras, perfect amount of phz and all that). My entire INTENTIONS.TXT is around 217 lines long now. I am experimenting with the best way to use rest phase. Right now it is running at --restevery 20 --restfor 20. I am not sensitive enough to draw any conclusions about this but since Anthro Heart had said it is stronger I take his word for that.
Also reden : not a single BSOD since Ubuntu. "... loading times as well as being in the same region that other users are, so that the energy reaches me in the same way it reaches everyone else." This is a bizarre perspective. Even with --imem 100, it would reach you the same way, as Repeater uses the same method to transfer the energy. The thing that changes is the size of the "gate", which allows more energy to pour out at once. Repeater's energy is effectively limitless and infinite. But how much of it pours out at a time is seemingly limited by the Repeat speed. It being faster helps to give every Intention more energy from the available bandwidth. Have you experimented with having 2 Repeaters running on the same file? Okay. I understand!
Now that you suggested it I am certainly trying it. I opened 5 Repeaters with imem of 8 GB and it has a much more notable effect on system performance. Load times are smooth at this memory setting. Since I have 5 windows * 8 GB, that should total to 40 GB. As I opened it I felt a pressure between my eyes, coincidential or not I do not know.
So you are saying this is a perfectly viable way to run the Repeater? I'm optimistic about it.
|
|
|
Post by reden on Jun 26, 2022 18:03:58 GMT
"... loading times as well as being in the same region that other users are, so that the energy reaches me in the same way it reaches everyone else." This is a bizarre perspective. Even with --imem 100, it would reach you the same way, as Repeater uses the same method to transfer the energy. The thing that changes is the size of the "gate", which allows more energy to pour out at once. Repeater's energy is effectively limitless and infinite. But how much of it pours out at a time is seemingly limited by the Repeat speed. It being faster helps to give every Intention more energy from the available bandwidth. Have you experimented with having 2 Repeaters running on the same file? Okay. I understand!
Now that you suggested it I am certainly trying it. I opened 5 Repeaters with imem of 8 GB and it has a much more notable effect on system performance. Load times are smooth at this memory setting. Since I have 5 windows * 8 GB, that should total to 40 GB. As I opened it I felt a pressure between my eyes, coincidential or not I do not know.
So you are saying this is a perfectly viable way to run the Repeater? I'm optimistic about it.
To me, it's the difference between one big spout and two smaller spouts, that regardless sum up to be as large as one. It also uses more cores if you have many sitting idle.
|
|
|
Post by sound on Jun 26, 2022 18:18:37 GMT
That is interesting. I noticed when I open many Repeaters, it cannot reach a limit of RAM. I can open Repeaters totaling 100 GB with a swap file of 50 GB and RAM of 8.
|
|
|
Post by AnthroHeart on Jun 26, 2022 18:19:57 GMT
That is interesting. I noticed when I open many Repeaters, it cannot reach a limit of RAM. I can open Repeaters totaling 100 GB with a swap file of 50 GB and RAM of 8. I can assure you Repeater is doing work even if it doesn't show full RAM usage.
I definitely feel it running.
|
|
|
Post by sound on Jun 26, 2022 18:26:07 GMT
That is interesting. I noticed when I open many Repeaters, it cannot reach a limit of RAM. I can open Repeaters totaling 100 GB with a swap file of 50 GB and RAM of 8. I can assure you Repeater is doing work even if it doesn't show full RAM usage.
I definitely feel it running.
I believe you!
I will use 4 Repeaters each with 12 GB of imem over the coming days. No particular reason but it feels right.
|
|
|
Post by AnthroHeart on Jun 26, 2022 18:29:45 GMT
Did 12GB of RAM cause the bug with the extra "T"? Or was it when you used a lot more RAM?
|
|