I upgraded to the latest Dart Editor (28355) both on Win7-32 and Win8-64 today. On Win7 it appears to run extremely slowly, on Win8 it is fine. Running both the Dart-Editor and the browser concurrently on Win7 I found unworkable. With just the dart-Editor running, it was still very slow to respond to input, but much better (4 v 25 seconds). I did reboot a couple of times in desperation. The Win7 machine is an older dual-core pentium with 4gb Ram running at about 2ghz (I'm on Win8 now). Previously I've had no major problems with the Dart-Editor on Win7 over a period of 6-months or more.
Is this a known problem with 28355?
Do you have a lot of folders in the 'Files' tab?
I find reducing the number of folders or right-clicking and selecting 'Don't Analyse' on some folders helps performance.
I have not experienced anything as dramatically slow as you have reported though.
I've found that 28355 uses much more RAM than before (about 1GB total now, for me). If you have a browser running and a couple of other programs, 4GB will be used up pretty fast and cause slowdowns. I'm not sure about the difference with Windows 8, perhaps it has better memory efficiency.
Related
I have an electron app that renders to a 1280x720 canvas and is using requestAnimationFrame. The app works perfectly on my machine running, 16GB ram, i7, x64, with a GTX 1080 GPU. When I run the same app on other computers it runs extremely slow. I have tried a surface go, but also my friends computer who is running much new and better hardware than mine and it still runs at a potatoes rate. Any idea what could cause this discrepancy?
I have tried using setInterval to see if there was a difference and there was a minimal difference but the app is still unplayable. I also tried to combine all my modules into a singleton as per their advice and I noticed a slight increase.
We are migrating our multi-threaded application to Delphi XE7 and are testing the new TParallel.For function. We have found that it parallelizes well on laptops (Core I-5/Windows 7 with 4 cores) achieving close to consistent 100% cpu usage.
When we run exactly the same code on an Intel Xeon/Windows 2008 R2 with 2x12 cores, it only achieves about 3% usage and appears to be only using 2 of the cores.
The same problem is evident using the Conways Life demo sample application.
We have tried using the OTL which parallelizes close to 100% on the Xeon, but unfortunately we have run into the "Not enough quota" issue and can't seem to resolve that, either.
Has anyone else run into this? We have tried using the Stride parameter, SetMinWorkerThreads and SetMaxWorkerThreads() methods but to no avail.
I am working on a huge Grails Project, and more and more people are going to be working on it.
The problem is that I have been spending ages setting up people's machines (java etc etc).
I heard that there is something like a VM that you can set up on your machine once and transfer on other people's computers.
Also what about performance issues? Lets say I install a VM on other people machine that will slow down things no?
Yes it will be very bad in performance as VM runs as a full fledged machine with OS on top of it. If you have all systems with very high configuration like quad-core i7's and minimum of 8Gb rams then only systems will be able to handle such load.
Still it will be a bad idea to do so. And while running grails you already have multiple instances of java running like in my case with netbeans I have 2 resource hungry java instances running with 700mb and 500mb respectively.
This is odd behavior but I have been able to reproduce it 100%. I'm currently testing Neo4j 2.0.1 Enterprise on my laptop and desktop machines. Laptop has 8GB RAM i7 4600U and Desktop has 16GB RAM i7 4770k. (Both machines are running Windows 8.1 x64 ENT and the same version of Java (latest as of FEB 19, 2014).
On first boot of each, when I run an expensive (or not so expensive) query, I can see the memory allocation go up (as expected for the cache). When starting the server, initial allocation is around 200-250mb, give or take. After a few expensive queries, it goes up to about 2GB, which is fine, I want this memory allocation. However, I have a batch script that stops the service, clears out the database and restarts the service (to start fresh when testing different development methods).
After 3 or 4 restarts, I noticed that the memory will NEVER climb above 400mb. Processor usage sits around 30-40% during the expensive query, but memory never increases. I will then get Unknown Error messages in the console when running other expensive queries. This is the same query that after a full reboot of the system, would bring the memory usage up to 2GB.
I'm not sure what could be causing this, or if there is a way to make sure that memory usage continues to be allocated, even on service restart. Rebooting a production server doesn't seem like a viable option, unless running in HA.
I have a Delphi (hence 32-bit) CGI app running on a Windows 2008 64-bit server that has 24 Gb RAM with IIS7. The web service runs fine for a few days at a time (sometimes a few weeks) and then suddenly starts reporting "Not enough storage available to process this command."
Now I've seen this before in regular Windows apps and it normally means that the machine ran out of memory. In this instance, the server shows that only 10% of physical RAM is in use. On top of that, TaskManager shows only one instance of the CGI executable, with 14Mb allocated. And once it starts it keeps giving the error, regardless of actual server load. No way is this thing really running out of memory.
So I figured there is probably some maximum memory setting in IIS7 somewhere, but I couldn't find anything of the sort. Restarting the web server makes the problem go away until next time, but is probably not the best strategy.
Any ideas?
It might be an IRPStackSize issue as discussed here. And the particular cause mentioned in that article is not the only one, apparently.
The CGI does not seem to ever unload under IIS7, even though it seems to work under IIS6. This seems to be a problem with the CGI support on IIS7.