| Pages:
1
..
13
14
15
16
17
..
54 |
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by jptann  | I ran the 50.60 release and with the system running, when I sorted on the F-F column and then highlighted the largest F-F, our old issue is back again
with a random strategy is then substituted. I am running one manager and 4 workers, utilizing 90% CPU and 95% system RAM.
Same old issue is back. It also appears in 50.55. Did I so something different this time?
Running from the GSB in the C: Drive. No special SSD drive on this computer. |
send me tv and I will look
|
|
|
jptann
Member
 
Posts: 101
Registered: 13-6-2017
Member Is Offline
Mood: No Mood
|
|
50.60 Release
Here you go.
|
|
|
jptann
Member
 
Posts: 101
Registered: 13-6-2017
Member Is Offline
Mood: No Mood
|
|
I also sent the TV our of help just now
|
|
|
coccigelus
Junior Member

Posts: 73
Registered: 11-7-2018
Member Is Offline
Mood: No Mood
|
|
Hello,
I am happily using the build 50.66. A couple of things:
Once I have completed the validation I note that the memory used is not dumped away but remain somehow still used. I see this from Task Manager after
a couple of minutes after completion still at 96%. Is that normal?
I would appreciate if We can have somehow between the multitude of beta versions the indication of a stable version. For instance a build that has not
improved with new features but has been fixed and corrected from previous versions.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by coccigelus  | Hello,
I am happily using the build 50.66. A couple of things:
Once I have completed the validation I note that the memory used is not dumped away but remain somehow still used. I see this from Task Manager after
a couple of minutes after completion still at 96%. Is that normal?
I would appreciate if We can have somehow between the multitude of beta versions the indication of a stable version. For instance a build that has not
improved with new features but has been fixed and corrected from previous versions.
|
Each build is better than the last currently. The last stable build will be soon, as secondary filters will start before too long, and then there will
be less updates.
Is the ram on the manager or the worker still high?
GSBram (now called GSBResource manager) will kill idle workers ans so ram will shrink. Managers we cant kill and ram can be high in them if there are
lots of systems. Ram often may reduce after a few minutes when cache is auto cleaned
|
|
|
coccigelus
Junior Member

Posts: 73
Registered: 11-7-2018
Member Is Offline
Mood: No Mood
|
|
I am using the standalone version. I am not using the manager and workers right now because I feel that for the server running my trading systems
live, the standalone version is less resource intensive. (and less problematic)
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by coccigelus  | | I am using the standalone version. I am not using the manager and workers right now because I feel that for the server running my trading systems
live, the standalone version is less resource intensive. (and less problematic) |
The manager will use less resources, as the standlone all you do is on your own pc
The manger will give you some free workers, but speed varies greatly with cloud use. Cloud user high the next few days as my machines are used making
the next video. Regardless there should normally be some free cloud for you.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Jan 09 2019
Untested fix for systems from stray workers appearing, results change and or no graphs. Manager only works with 50.72 workers, so there is no cloud
power for 48 hours till this is tested. (apart form your own workers)
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Has 50.72 fixed the systems from other users might appear in the manager?
The GSB cloud is now on 50.73.
50.72 has run worker minimized option. Needed to make GSB Resource Manager run better
Just realized, Workers older than 50.72 wont work on the free GSB could.
I will try to fix < 24 hours, but best any one who wants the cloud goes 50.72 or above
Bug fixe and updates shown

|
|
|
coccigelus
Junior Member

Posts: 73
Registered: 11-7-2018
Member Is Offline
Mood: No Mood
|
|
Hello,
Where is located the GSBresourceManager?
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
I will upload today.
The latest GSB Help file has the docs
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Resource manager is here.
https://trademaid.info/forum/post.php?action=edit&fid=2&tid=...
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
1.0.50.81 / 2019-01-17: under testing
Force custom indicator fixed. Some exceptions errors fixed.
WF astab and rstab now in unique systems grid, so can be used to derive stats.
Fix WF coulomb sort.
50.79 Released only via GSBresourceManager
Has improvements in WF cloud reliability.
1.0.50.78 / 2019-01-12:
A fix (exception trap) for cases where GSB cannot read processor name.
A fix for sound/app (ex. ding.wav) file not found (by try to locate missing file in GSB's local folder).
A fix for systems leak from previous manager settings.
Implemented more effective public cloud usage
OptimizePriceData default set to false.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
1.0.50.82 / 2019-01-17:
fix GSBManger not responding when 100's of WF are submitted.
(Manager came good only after all WF processed)
File in GSBResourceManager now
|
|
|
coccigelus
Junior Member

Posts: 73
Registered: 11-7-2018
Member Is Offline
Mood: No Mood
|
|
Just a report between ver 1.0.50.79 & 1.0.50.82 . There is not compatibility with saved system between the two versions. (net profit and others
metrics wrong )
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by coccigelus  | Just a report between ver 1.0.50.79 & 1.0.50.82 . There is not compatibility with saved system between the two versions. (net profit and others
metrics wrong )
|
This should not be the case. Send me teamviewer details and I will look.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Under testing
1.0.50.83 / 2019-01-19:
Fixed/Improved WF cancel (by multiple attempts and locking) and re-submit logic (faster and resources-friendly).
A Minor fix in WFs cancel all on manager/worker close.
Updated TPD, OOS, and WFP to have Yes/No sub-buttons (instead of a single click button).
Added OOS to user tasks (in right grid).
Fixed TPD and WFP user tasks (no updates).
Added "Reset App Settings" and "Reset Optimization Settings" button under File menu.
Fixed null exception on TPD on single price data.
Fixed exceptions logging to allow file path up to 260 letters (instead of 160).
Fixed exception message on some cases of thread cross.
Minor GUI fixes and updates here and there.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Under testing
1.0.50.84 / 2019-01-21:
Fixed "Periods Mode" Dates (by setting default PerformancePeriodName to "Full Period" and including it in full period's performance, graph, and
trades).
Minor GUI updates.
|
|
|
jptann
Member
 
Posts: 101
Registered: 13-6-2017
Member Is Offline
Mood: No Mood
|
|
Peter:
Don't see any of these updates to 50.83 in resource manager. Where can I find them?
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Send me teamviewer details & I will look. 50.84 is what should have been downloaded.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
50.89 released. Jan 24 2019
Note I have not released the new ts coded needed for the new exits. It will be a day or so away as the code will change.
The default is all new exits are true. This is a bad idea and needs to be fixed in the next build.
Its likely systems with the new exits may not be compatible with the next build, so consider this a sneak preview
old workers will not work with this build.
There are minor TS code verification issues with the new exits.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
50.90 under testing. Should have all the small bugs fixed, and new ts code.
Out in 24 hours if it passes testing.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
50.90 released. New eld also should end up in manager and or worker folder
GSB_SCRIPTS_2019_01_24+WithupdatedGsbsys1ES.eld
Note the exit numbers DO NOT correspond to the post shown on 50.80 above.
Exit2 (old5) I think will be best for ES.
There is one bug. Name of eld exits too long. shorten them.
// Decision Exit (I/SF)
If flag = 0 And CurrentContracts > 0 AND GSB_DecisionExit(decision, sfDecision, 2) = 1 Then
Begin
BuyToCover("SX-IFlatRevAndSFFlatRev") this bar on close;
Sell("LX-IFlatRevAndSFFlatRev") this bar on close;
End;
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
50.91 Fix for the above TS code issue coming soon
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
50.91 released via resource manager. Help file updated inc info on the 7 new exits. Recommend not to use all 7 at once, but this is not critical
|
|
|
| Pages:
1
..
13
14
15
16
17
..
54 |