| Pages:
1
..
18
19
20
21
22
..
54 |
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by jptann  | Peter, can't find the new release anywhere. I will send you an email with a tV to see if you can fix.
Thanks in advance |
There was a very simple problem on my end. This affects all users in that update didnt occur.
I updated your rm to the newest version too
Peter
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
vip note. GSB 52.16 manager will not work with older workers. But old managers will work with 52.16 workers
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Under testing. GSB 52.18. Can load and save macro's
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
May 2 2019 52.18 released.
Load / save macros
https://trademaid.info/gsbhelp/Macros.html
|
|
|
avatartrader
Junior Member
Posts: 60
Registered: 1-10-2018
Member Is Offline
Mood: No Mood
|
|
I am using 52.18 and running through the indicator testing as outlined in the docs and the video, and I have observed that the memory and CPU on my
Manager (running on my PC) is much higher than I would expect. The CPU is running at 20-40% (not constant, but in sustained bursts) and the memory is
up to over 16GB, which seems extreme considering the manager is not building any systems. I have stopped and restarted the process a couple of times
to correct a couple of things in the optimization settings between tests, but have not been doing anything too extreme - I did not close and restart
GSB between runs. At minimum, there seems to be a memory leak in the application...
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by avatartrader | | I am using 52.18 and running through the indicator testing as outlined in the docs and the video, and I have observed that the memory and CPU on my
Manager (running on my PC) is much higher than I would expect. The CPU is running at 20-40% (not constant, but in sustained bursts) and the memory is
up to over 16GB, which seems extreme considering the manager is not building any systems. I have stopped and restarted the process a couple of times
to correct a couple of things in the optimization settings between tests, but have not been doing anything too extreme - I did not close and restart
GSB between runs. At minimum, there seems to be a memory leak in the application... |
I observed this too on saturday. GSB is not idle. Its decompressing systems, then has to run them to get the performance metrics. Regardless this has
now been made effective. (might be using the binary of the systems instead of ascii - internally) So there is a fix for this. I can send you a copy,
but its not well tested.
|
|
|
avatartrader
Junior Member
Posts: 60
Registered: 1-10-2018
Member Is Offline
Mood: No Mood
|
|
Thanks, Peter - the only other thing that I noticed is that both when I built 40k systems for indicator testing and 50k systems for a test build, GSB
did not stop at the limit in either case. When I was doing the 50K run today, I dozed off around 40k and when I woke up it was still running and I had
62k.
On my servers, I did notice that RM was in the Stopped state (but the app was still running, not crashed), so it seemed to have stopped automatically,
but workers were still producing systems.
Earlier yesterday when I did a quick test of 1000 it stopped by itself, so I'm not sure if the issue is just that I have not closed and re-opened GSB
or the associated components between runs or something else.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by avatartrader | Thanks, Peter - the only other thing that I noticed is that both when I built 40k systems for indicator testing and 50k systems for a test build, GSB
did not stop at the limit in either case. When I was doing the 50K run today, I dozed off around 40k and when I woke up it was still running and I had
62k.
On my servers, I did notice that RM was in the Stopped state (but the app was still running, not crashed), so it seemed to have stopped automatically,
but workers were still producing systems.
Earlier yesterday when I did a quick test of 1000 it stopped by itself, so I'm not sure if the issue is just that I have not closed and re-opened GSB
or the associated components between runs or something else. |
Some of the newer builds of RM did not work well. I have a likely fix, but have not tried it. (its just been made). Getting too many systems is more
likely when you have only 30 min bars, not 29,30,31. The reason is 30 min only build much faster then 29,30,31. Once you hit 50k workers, the manager
will send stops to the workers. However the workers take some time to stop. So there is grace period (under app settings) to stop systems coming in x
seconds after the manager has stopped. However this doesnt work perfectly - though a lot of time was spend trying to fix this. (its a minor bug)
RM doesnt stop gsb manager running, it just controls the amount of workers, and wht group of workers are allowed to run. Having rm stopped is a bit
dangerous, as you may run out of ram.
|
|
|
avatartrader
Junior Member
Posts: 60
Registered: 1-10-2018
Member Is Offline
Mood: No Mood
|
|
In this case, I was building 29,30,31 and they just never stopped (all running 52.18). The manager hadn't even stopped - I had to click the stop
button manually.
I did run out of RAM on one server. I did not stop RM, it stopped on it's own at some point. I just upgraded to 20190428.1 yesterday and this is the
first time I recall seeing that happen.
Last night, I only had it stop on it's own on one of the servers, and today it happened on both of my servers.
I don't see anything in the logs either. However, I do see one line about C:\...\ReduceMemory.exe" is missing on one of the servers, but I don't have
that on any of the machines and doesn't appear to be related.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by avatartrader | In this case, I was building 29,30,31 and they just never stopped (all running 52.18). The manager hadn't even stopped - I had to click the stop
button manually.
I did run out of RAM on one server. I did not stop RM, it stopped on it's own at some point. I just upgraded to 20190428.1 yesterday and this is the
first time I recall seeing that happen.
Last night, I only had it stop on it's own on one of the servers, and today it happened on both of my servers.
I don't see anything in the logs either. However, I do see one line about C:\...\ReduceMemory.exe" is missing on one of the servers, but I don't have
that on any of the machines and doesn't appear to be related.
|
check you have ReduceMemory.exe in the rm folder
Here is the latest RM. It has one bug that on i7 5930 cpu, cpu is Nan (not a number)
There are new feature in this build. It pulls in sub folders of GSB. Needed to get the GSB macros. + bug fixes. Worse case use RM 201902xx build
Attachment: Login to view the details
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
This RM has all known bugs fixed and downloads gsb sub folders.
Put this in your current RM folder. Its critical to not run RM and gsb in the same folder. There will be a dll version conflict
Attachment: Login to view the details
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
May 6th 2019. 50.21
Ram and CPU improvement of manager.
Minor bug fixes.
Stats G&H doesnt work yet.
Operand "-" now included. This means you dont use weights say -10 to 10 step 2, but would use weights 2 to 10 step 2, and allow operand + and -
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
TO BE CONFIRMED - CRITICAL BUG
50.21 MAY BE A BAD BUILD. THE SCRIPT IN GSB <> SAME SCRIPT IN GSB TS CODE.
WORKING ON IT NOW.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
May 7th 50.22 released.
Fix for bug. Turns out its been there for a number of builds, and was only apparent in WF
|
|
|
avatartrader
Junior Member
Posts: 60
Registered: 1-10-2018
Member Is Offline
Mood: No Mood
|
|
I am using 50.22 and the memory and CPU utilization is back to normal. After building 40K, my GSB RAM for the Manager is at 3.5GB instead of 29 GB.
The build process also stopped this time shortly after building the systems and the RM did not stop involuntarily on any of the machines (latest
version 0506).
|
|
|
avatartrader
Junior Member
Posts: 60
Registered: 1-10-2018
Member Is Offline
Mood: No Mood
|
|
One thing I am noticing is that as my Macro is running (the steps for indicator validation) and it is saving stats, the notification is indicating
that it is saving stats for 10000 systems, and not the full amount of a little over 40k, whereas when it completes the change for Nth mode, the
notification cites the full amount.
Is this merely an error in the notification, or a bug where it is only calculating stats for 10000 systems? Looking at the raw results, it seems like
it may be the former, but can't tell for sure.
Update: If I hover over the "Statistics" column, it shows the contents of each as only 10000 as well.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by avatartrader | One thing I am noticing is that as my Macro is running (the steps for indicator validation) and it is saving stats, the notification is indicating
that it is saving stats for 10000 systems, and not the full amount of a little over 40k, whereas when it completes the change for Nth mode, the
notification cites the full amount.
Is this merely an error in the notification, or a bug where it is only calculating stats for 10000 systems? Looking at the raw results, it seems like
it may be the former, but can't tell for sure.
Update: If I hover over the "Statistics" column, it shows the contents of each as only 10000 as well. |
Check this setting is on 100,000 not 10,000
If that doesnt work email me teamviewer.com details
|
|
|
avatartrader
Junior Member
Posts: 60
Registered: 1-10-2018
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by admin | | Quote: Originally posted by avatartrader | One thing I am noticing is that as my Macro is running (the steps for indicator validation) and it is saving stats, the notification is indicating
that it is saving stats for 10000 systems, and not the full amount of a little over 40k, whereas when it completes the change for Nth mode, the
notification cites the full amount.
Is this merely an error in the notification, or a bug where it is only calculating stats for 10000 systems? Looking at the raw results, it seems like
it may be the former, but can't tell for sure.
Update: If I hover over the "Statistics" column, it shows the contents of each as only 10000 as well. |
Check this setting is on 100,000 not 10,000
If that doesnt work email me teamviewer.com details |
Yes, that was the issue. Thanks!
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Under testing. 52.23
We can now build systems with weight of 1 only, then use soft coded variables in WF
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
May 11 2019 released. 52.28
Has more improvements to WF and bug fixes.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
May 15 05 2019. 52.30 under testing.
Has bug fix for macros cant be used after they are canceled.
Extra macro features not added just yet, but not far away
In 52.31 we hope to have.
Macros can select the top 1000 systems by np/dd etc
macros can play sound / send email. The feature appears to be in 52.28 but isnt fully coded.
Possibly a counter to show how many systems you have selected.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
52.30 released
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
May 17 2019. 52.32 under testing
Has find a system. Search IS cAse Sensitive
Macro addition
Has add top systems into favorites
has send email //Make sure smtp settings are set under app settings
has play sound
has number of systems chosen in bottom of GUI
 
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
May 17 2019. 52.32 released. See above for more details
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
May 22 2019 52.33 under testing.
It has WF to EWFO (in manager only for this build)
It also drives workers harder during WF so they are idle less.
 
|
|
|
| Pages:
1
..
18
19
20
21
22
..
54 |
![[*]](images/davis/default_icon.gif){kind=icon}
