2nd May 2008

Microsoft Mesh Second Impressions

posted in Technology, Microsoft, Software |

I mentioned last week that I was going to have a hard time playing with Mesh because it won’t run with UAC disabled. First of all, Microsoft did post an explanation of why the current version requires UAC. I understand the explanation, but it is one of the typical cases where teams have to build on this internal technology and that one and this other one, none of which are ready for prime-time and all of which aren’t necessarily focused on actually providing user value…

In any case, I did install it on two XP machines. I’m about to shut it off. I noticed one of them was running a bit slow lately and checked the task manager. Mesh is using 490MB of memory, and has consumed 9 hours of CPU over the past couple of days. And in case it wasn’t clear, I haven’t really been asking it to DO anything…

I’m also mildly annoyed that the process is named “Moe.exe” so it took a small amount of digging to figure out what it was that was consuming all my system resources. They also have a second process called MoeMonitor.exe that somehow has consumed over 1.25hours CPU and 33mb RAM. It appears to be responsible for the task-bar icon.

There are currently 2 responses to “Microsoft Mesh Second Impressions”

Why not let us know what you think by adding your own comment! Your opinion is as valid as anyone elses, so come on... let us know what you think.

  1. 1 On May 19th, 2008, Duffergeek said:

    MOE stands for Mesh Operating Environment. Get it?

    Still, that is a lot of CPU if you aren’t actually syncing anything yet.

  2. 2 On June 20th, 2008, Emre Aydinceren said:

    Exact same experience. Not syncing anything, not being used, it was consuming 40% on a Dual Core machine

Leave a Reply