Quick question for other people using this software… How much RAM does your whatpulse use on average?
I noticed that my WhatPulse is almost constantly using 250mb of ram, which seems like a lot to me given what the program does.
I think one the reasons this is happening is because I’ve kept the same “whatpulse.db.backup” and “whatpulse.db” file for the past many computer reformats so I don’t lose the local stats of my computer. (Which it would be really nice if these could be backed up to a cloud).
These two files are both 194mb which also seems like a lot, and I think that could be the reason why.
Again, I’m sure if I was willing to delete these files and restart my client (which would reset my local stats) it would fix the issue, but I’m not willing to do this.
I have over 8gb of ram in my computer, so 250mb isn’t very much.
I appreciate the interest in fixing this “issue”. However, when I try to install 2.4.1b1, I get a “QtWebKit4.dll” error. Most of the time I encounter .dll errors, they are because of C++ frameworks or Directx not being installed. I’m not sure what could be causing this .dll error, however, considering that previous versions work just fine for me.
I have also tried compatibility mode, which did not help, either.
Could this possibly be an issue with my computer, or from the program’s end?
Currently using an intel i7-2600, x64, Windows 7 Ultimate
Not sure if there are other specs that would help.
I’m sorry, should have specified: the download is the client, not an installer. You can just drop it in your current installation directory (c:\program files\whatpulse) and run it instead of the your current whatpulse.exe. That way you won’t loose your current client version.
The 2.4.1b1 already does that, so you can leave your 200MB database in place, run it for about 24 hours - it will have pruned the database by then. The actual resizing the database file happens upon the exit of the client, so you will need to restart it to have effect.
But it’s good to know it actually is the database size in your case…I’ll see if I can get any deeper on the database end, as it’s third party code at the moment.
Actually looking forward to @dullahan8 's response, as he mentioned closing the window helps his case.