FYI: When running an optimization on a parameter or parameters (I haven’t noticed a difference in behavior whether one or multiple parameters or any specific parameters) if I happen to attempt to switch windows away from the strategy running the optimization just as (or immediately before) the optimization appears to be compiling its results WL freezes causing an “hourglass” to appear which does not go away. The only remedy seems to be terminating and then restarting WL. If I haven’t saved the workspace just before this occurs any changes made since the last save are lost. WL also similarly freezes if I happen to be actively working on a strategy in another window (e.g., scrolling results) when the optimization begins to compile its results. WL does not seem to freeze while the optimization is processing – only when it seems to be completing the process. This occurs when running as administrator or not.
Rename
You forgot to tell us which optimizer this is happening with? Have you tried different optimizers, and if so, which ones fail and which do not?
The real question is why is this happening with only your machine and not everyone else's? I optimize all the time, and I have never seen this problem. When did this start to happen? How much memory do you have in your machine?
If it's unique to your machine, it might be a memory management problem. Have you flashed the BIOS lately? (The BIOS drives the MMU [Memory Management Unit] of the processor.) Have you tried running an extensive memory diagnostic on your system? Have you tried reproducing the problem on another machine?
The real question is why is this happening with only your machine and not everyone else's? I optimize all the time, and I have never seen this problem. When did this start to happen? How much memory do you have in your machine?
If it's unique to your machine, it might be a memory management problem. Have you flashed the BIOS lately? (The BIOS drives the MMU [Memory Management Unit] of the processor.) Have you tried running an extensive memory diagnostic on your system? Have you tried reproducing the problem on another machine?
From your description it seems to be freezing during the population of the visualizers, which needs to happen in the main UI thread. Do you have any third party extensions installed?
I'll second superticker's comment. I was having this issue until I reflashed my BIOS. Since then I've not run into any problems.
Thank you for your helpful thoughts and information.
The computer I run WL on has 32gb of RAM and, per task manager, I don’t think I have ever seen WL actively using more than 4-5,000mg, although it is authorized to use more. I have not tried to replicate the problem with my “trading computer” which has 64gb of memory, so maybe I should try that even though I will not continue to run WL on that machine.
I generally use optimizations to get a rough idea of the scope of possible results from changing the parameter settings so I seldom use anything other than “shrinking window” with a fairly low number of total permutations as the optimization method. I have not added any third-party software to WL. I have also not tried to “flash my BIOS” so I might try that as well, although it concerns me that I might get arrested if I try it in a public setting.
Anyhow, I just wanted to point out that this was happening to me and if it is systemic and there is any easy fix, it probably makes sense to do it. I can live with it the way it is, I guess I just need to be thoughtful about when I initiate an optimization routine.
The computer I run WL on has 32gb of RAM and, per task manager, I don’t think I have ever seen WL actively using more than 4-5,000mg, although it is authorized to use more. I have not tried to replicate the problem with my “trading computer” which has 64gb of memory, so maybe I should try that even though I will not continue to run WL on that machine.
I generally use optimizations to get a rough idea of the scope of possible results from changing the parameter settings so I seldom use anything other than “shrinking window” with a fairly low number of total permutations as the optimization method. I have not added any third-party software to WL. I have also not tried to “flash my BIOS” so I might try that as well, although it concerns me that I might get arrested if I try it in a public setting.
Anyhow, I just wanted to point out that this was happening to me and if it is systemic and there is any easy fix, it probably makes sense to do it. I can live with it the way it is, I guess I just need to be thoughtful about when I initiate an optimization routine.
QUOTE:
I have also not tried to “flash my BIOS” so I might try that as well, although it concerns me that I might get arrested if I try it in a public setting.
You're saying that you are running WL on a public computer?
Public computers are not well maintained, so their BIOS has probably never been flash upgraded. And you're trying to run an application (like WL) with a very large memory footprint, which will surely stress the MMU of the processor and its firmware (i.e. the BIOS)--that's your problem.
For any application requiring a large memory footprint and as demanding as WL, I would run it on the best hardware you have, and I would keep that hardware as well maintained as possible.
I don't know if you understand how the MMU works, but an application process is only allocated about 5 pairs of mapping registers in the MMU. But that won't be nearly enough for an application as demanding as WL, so the firmware has to juggle those 5 pairs to simultaneously address the entire WL application. Apparently, the firmware is struggling to do that, and that's why it needs updating. However, for less demanding applications (with better "Principle of Locality"), the old firmware should work fine.
Sometimes it can take the motherboard manufacture 2 or so years to find all the latent bugs in the MMU firmware, so I would give your motherboard one final flash after it's 3 years old. The manufacture won't develop anymore firmware updates after the motherboard is out of production, which is about 3 years typically.
No - that was supposed to be a joke - a pretty feeble one I guess.
Your Response
Post
Edit Post
Login is required