Project Mercury V1.2.7.1 released

A small bug fix release

– Fixed pause icon error in 32bit version
– Fixed typo Recieved to Received in balloon tip
– Unified punctuation in history tab

Current stuff I am working on for Project Mercury
– I/O priority adjustment
– Excessive mode CPU usage improvement
– Excessive mode customization

I am also working on a CPU bottleneck measuring tool. Which I hope will help people get better information to base computer upgrades on. Especially gamers.

– SvenBent

Crash issue hopefully fixed

The prior reported crash issue with Project Mercury V1.2.7.0 seemed to be a simple compiler/compression bug. All crash reports came from the public version and not from the donation version. After recompiling the crash issue seems to be gone.

Thank you to all of you that brought this to my attention, and helped out by providing feedback and system information.


Project Mercury 64bit crash issue reported

Multiple reports on Project Mercury 64 bit crashing at startup reported. This issue seems to be with certain system as not all people are seeing this behavior.

If your Project Mercury 64bit version is crashing, but 32bit works flawlessly. Please ,if possible, report your system specifications such as

  • Windows Version
  • CPU make and model
  • Are you running with administration right? UAC enable/disabled ?
  • Antivirus software
  •  or any other information you might think can influence this.

Thank you for all the help. Hopefully I will be able  to fix this soon

– SvenBent


Project Mercury V1.2.7.0 is released

– Implemented “Excessive mode”.
– Fixed typo “Implanted” to “Implemented”.

Excessive mode  monitors for background processes using more that 50% CPU time and lowers their CPU priority to “Below Normal”, thereby reducing the amount of CPU resources they “steal” from the main program.

This feature use a small amount of CPU resources on the monitoring part, so it is advice to only use in cases where the main feature is not enough, to keep operations smooth under heavy multitasking load.

Excessive mode ready

Excessive mode is finally ready in its standalone form, and is available to download for donators. Hopefully it should be merged into Project Mercury within 1-2 weeks.

Excessive mode still uses approximate twice the CPU resources of Bitsum’s Process Lasso, but hopefully future tweaks and optimizations will get it below.

Project Mercury without excessive mode enabled, still use far less CPU and memory than Bitsum’s Process Lasso as well as Process Tamer due to its none cyclic behavior.

– SvenBent

Excessive mode in development

Excessive mode is again under development. A separate very basic alpha trial of Excessive mode has been uploaded to the donators folder for testing.

The current alpha has some limitations and known issues:

  • Currently very slow to update adjust priority when CPU load changes  (1-3 seconds)
  • Hardcoded for 50% load on an 8 core CPU
  • Unoptimized code in regards to memory usage
  • Unoptimized code in regards to CPU usage

Feedback very welcome especially on CPU usage.

– SvenBent