In my case it is the import time from WD log files I am struggling with. It is definitely differences between computers when importing local log files for. I tried to compare 4 computers with the same set of log files. Downloading time, cull and append were almost the same, around 2 minutes, on all 4 but importing log files…
8 yr old wx server: 6 minutes
3yr old desktop: 4 minutes
3yr old laptop: 5 minutes
New wx server: 10 minutes
Might have been a bad choice of server but it works pretty fine in all other ways. For instance unpacking archives and calls to databases works much faster. Do you have time to test the log files I sent?
Thanks for all ideas but I have tried as an administrator and I have tried using log files from earlier this year without any improvement. Do know what is left to do…
Are the log files local on the computer you’re using? If you’re streamibng that data in from another computer, that could slow things down, perhaps. Again, it took me about 20 seconds, and my computer is not especially fast.
If you are in fact bringing the data in from another computer (via a web connection) then perhaps you could try transferring the file in its entirety to the local machine before attempting the import from it.
Let me know if that is the case, and whether this suggestion helps.
I have an up-to-date PC and I still run WXSimate & WXSim 10 minutes apart in case of slow internet connection, as that can double the download time and a fast PC makes no difference.
I’m still mystified by this, as when I test it on my (very average and a few years old) computer, it does the job in about 20 seconds per month (it could take 40 near the end of a month, when it looks at almost two whole months). Somehow the streaming of the data is different on different computers. I wonder if it’s a Net Framework issue (though I’m using a rather old version, I think).
Does anybody out there have the same experience as me (less than a minute to read the log files), or is this 10 minute thing common?
Meanwhile, putting the extra delay between WXSIMATE and WXSIM runs does sound like a solution (other than having to wait 10 more minutes for the forecast).
4-10 seconds, I envy you
But perhaps I’ll get there some day.
I’am gald you have not give up on this yet. I have some problems even with 16 minutes delay.
Do not know if this is helpful and how .NET works at all but like I wrote, I’m on a 64-bit system and perhaps the system is using alternative frameworks. Looks like I have the following versions installed:
32-bit: v1.0.3705, v1.1.4322, v2.0.50727, v3.0, v3.5, v4.0.30319
64-bit: v2.0.50727, v3.0, v3.5, v4.0.30319
Tom, do you think I shloud look around for eaqrlier versions of 64-bit frameworks?
Updates are easy.
Just go to the WXSim download page (http://www.wxsim.com/dnld) and click to download the second file in the list called WXSIMUPG.EXE.
Make sure none of the WXSim programs are running on the PC (WXSim, WXSimate & Wret) and then install the WXSIMUPG.EXE file in the normal way.
It’s worth reading through the release notes as there have been a couple of changes. It may also be worth making a backup copy of the whole WXSim folder before you install the new version.
DEFINITELY you should always try upgrading to the latest version first. I’m just about always working on refining the program, not only adding new features, but also fixing bugs as they pop up with widespread use in these very complex program. Some users understandably do like to lay back a bit before installing a new version, especially if they’re not experiencing any problems, just in case any new bugs are introduced, but 12.8.8 has been out for quite a while now, and seems to be the best yet. There have certainly been a lot of improvements in the last year, and upgrading takes only seconds, so please do so (again, using WXSIMUPG.EXE … NOT the demo).
