Server build type

[Michael Nemtsev]

If I specify the <gcServer enabled="true" /> in the config file
what's the way to determine the real mode the application was buit - server
or workstation?

Any way to use PerfCounters to detect that the mode is server, like GC Heap
number?

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch

 

[Willy Denoyette [MVP]]

| If I specify the <gcServer enabled="true" /> in the config file
| what's the way to determine the real mode the application was buit -
server
| or workstation?
|
| Any way to use PerfCounters to detect that the mode is server, like GC
Heap
| number?
|
| ---
| WBR,
| Michael Nemtsev :: blog: http://spaces.msn.com/laflour
|
| "At times one remains faithful to a cause only because its opponents do
not
| cease to be insipid." (c) Friedrich Nietzsche
|
|

The gcServer attribute determines the type GC to be used. This has nothing
to do with the application build mode. The server GC is only available on
multi CPU boxes and is only meant to be used by server applications
(non-UI). The server GC runs the GC on separate threads (one per CPU) from
the user threads.
There are no Perfcounters available that tell you what GC type you are
running against, all you can do is loas sos.dll in the debugger and issue
the !eeversion command.

Willy.

 

[Michael Nemtsev]

Hello Willy Denoyette [MVP],

W> | If I specify the <gcServer enabled="true" /> in the config file
W> | what's the way to determine the real mode the application was buit
W> -
W> server
W> | or workstation?
W> |
W> | Any way to use PerfCounters to detect that the mode is server, like
W> GC
W> Heap
W> | number?

W> The gcServer attribute determines the type GC to be used. This has
W> nothing
W> to do with the application build mode. The server GC is only
W> available on
W> multi CPU boxes and is only meant to be used by server applications
W> (non-UI). The server GC runs the GC on separate threads (one per CPU)
W> from
W> the user threads.

Yep, it's known

W> There are no Perfcounters available that tell you what GC type you
W> are
W> running against, all you can do is loas sos.dll in the debugger and
W> issue
W> the !eeversion command.

As I understand, there I should see more than one GC heap?

The final idea I'm trying to reach is to find out the permormance dependence
between of gcServer and gcConcurrent.
This two options is exclusive. Server mode (gcServer) creates number of GC
heaps, that depends on processor number and thus blocks using concurrent
GC (gcConcurrent) and gcConcurrent works only in workstation mode

But now I just want find the way to decect with type I'm running against

I wonder if somebody performs such tests, what's the advantage in using gcServer
vs gcConcurrent in multiprocessor clusters?

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

 

[Guest]

using tasklist /m mscorwks.dll i can detect the mode my app is running.

The performance issue is open "what's the advantage in using gcServer vs
gcConcurrent"

| If I specify the <gcServer enabled="true" /> in the config file
| what's the way to determine the real mode the application was buit -
server
| or workstation?
|
| Any way to use PerfCounters to detect that the mode is server, like GC
Heap
| number?
The gcServer attribute determines the type GC to be used. This has nothing
to do with the application build mode. The server GC is only available on
multi CPU boxes and is only meant to be used by server applications
(non-UI). The server GC runs the GC on separate threads (one per CPU) from
the user threads.
There are no Perfcounters available that tell you what GC type you are
running against, all you can do is loas sos.dll in the debugger and issue
the !eeversion command.

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

 

[Willy Denoyette [MVP]]

That true for V1.X only, V2 uses the same mscorwks.dll for both server and
workstation GC.
If you want to know what GC version your application is using, you can read
the GCSettings.IsServerGC property, or you have to look into your
xxx.exe.config file.
The GC server is optimized for 'throughput' (server applications), there are
as many GC heaps as their are CPU's, and each heap has it's own GC thread.
That means that a GC doesn't run on the user thread, and the user thread can
run in parallel with a (single) GC thread. Typical UI style of applications,
aren't supposed to stress the GC as much as server applications, the UI
thread is mostly idle so it won't hurt to run the GC on this thread for gen0
collections.
If you have a windows application that runs a number of background threads
who's allocation scheme show large allocation rates, you might take
advantage of the server GC, but as always when talking about performance,
you have to measure.
Willy.


message | using tasklist /m mscorwks.dll i can detect the mode my app is running.
|
| The performance issue is open "what's the advantage in using gcServer vs
| gcConcurrent"
|
| "Willy Denoyette [MVP]" wrote:
|
| >
| > | > | If I specify the <gcServer enabled="true" /> in the config file
| > | what's the way to determine the real mode the application was buit -
| > server
| > | or workstation?
| > |
| > | Any way to use PerfCounters to detect that the mode is server, like GC
| > Heap
| > | number?
| > The gcServer attribute determines the type GC to be used. This has
nothing
| > to do with the application build mode. The server GC is only available
on
| > multi CPU boxes and is only meant to be used by server applications
| > (non-UI). The server GC runs the GC on separate threads (one per CPU)
from
| > the user threads.
| > There are no Perfcounters available that tell you what GC type you are
| > running against, all you can do is loas sos.dll in the debugger and
issue
| > the !eeversion command.
|
| ---
| WBR,
| Michael Nemtsev :: blog: http://spaces.msn.com/laflour
|
| "At times one remains faithful to a cause only because its opponents do
not
| cease to be insipid." (c) Friedrich Nietzsche
|

 

[Guest]

That true for V1.X only, V2 uses the same mscorwks.dll for both server and
workstation GC.

And does the gcServer on the V2 set to the server mode?

--
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

 

[Willy Denoyette [MVP]]

message |
| "Willy Denoyette [MVP]" wrote:
|
| > That true for V1.X only, V2 uses the same mscorwks.dll for both server
and
| > workstation GC.
|
| And does the gcServer on the V2 set to the server mode?
|


Sure, under condition that number of CPU's is > 1.

Willy.