New DNet client- console vs. core view?

[Athlex]

Does one view have more CPU overhead than the other? I've tried to do some tests for keyrate with the core view and the console view, but can't get anything conclusive. Naturally, I want to maximize my keyrate, but the core view does look cooler. 🙂

 

[Phil00]

This might be just me noticing something out of nothing, but I seem to get better processing in the core view.

----------------
Phil.
Abit VP6
Dual PIII700's @ 1000
2x256Mb Crucial CAS2 @ CAS2
2xIBM Deskstar 75GXP's in RAID0
RC5 Stats

 

[ViRGE]

The core should get a slightly worse rate than the CLI mode; so unless anyone can prove otherwise, what you're seeing is most likely just some flux in the way the core mode gives it's keyrate.

 

[Slacker]

What does this new client look like? I am still using the original GUI.

 

[ViRGE]

I don't think there are any screenshots yet, so you'll have to download the client and try it out.

 

[Athlex]

Slacker,
The new GUI client is quite cool. It has a "file/edit" style menu at the top of the window that allows you to access the functions that you'd normally have to right-click for. It also gives the option of a "core view" instead of the standard client console. This view is very much like the task manager in Windows NT where it's got a line graph to depict keyrate and it actually tells you what your keyrate is on the fly. It's quite cool to be able to see how running other programs affects your keyrate. I'm just trying to see if I can tell whether the graph view slows the keyrate any more than the normal console view.
atx

{edit} The file/edit menu is also a godsend for running a gui client without a mouse. I still can't figure out how to restore the client window if I minimize it, tho...

 

[Jani]

One, actually two screenshots, now available at http://guru.rdx.net/dnet/.

 

[Jani]

Dasm it