D
DC
Hi,
I am porting an app from Framework 1.1 to 2.0 and I am now using
Dictionary objects instead of Hashtables. There are some
lock (theHashtable.SyncRoot)
statements in the 1.1 code and I replaced those by
lock (theDictionary)
statements. I did not note a difference, but I wanted to ask if this
generates any issues like more granular locking.
I swapped out the Hashtable in the first place because I was hoping
that this would safe some memory. I am observing the following: under
1.1, my app is using p to 1300 MB of memory and running fine. With
2.0, the app is now using about 1100 MB of memory and then starts
throwing "out of memory" exceptions (2GB RAM Windows 2003 machines). I
have not found a way to solve this by cofiguration, and I am therefore
trying to save RAM now. Can someone recommend a really easy method to
profile which objects use what amount of RAM?
TIA for any hints,
Regards
DC
I am porting an app from Framework 1.1 to 2.0 and I am now using
Dictionary objects instead of Hashtables. There are some
lock (theHashtable.SyncRoot)
statements in the 1.1 code and I replaced those by
lock (theDictionary)
statements. I did not note a difference, but I wanted to ask if this
generates any issues like more granular locking.
I swapped out the Hashtable in the first place because I was hoping
that this would safe some memory. I am observing the following: under
1.1, my app is using p to 1300 MB of memory and running fine. With
2.0, the app is now using about 1100 MB of memory and then starts
throwing "out of memory" exceptions (2GB RAM Windows 2003 machines). I
have not found a way to solve this by cofiguration, and I am therefore
trying to save RAM now. Can someone recommend a really easy method to
profile which objects use what amount of RAM?
TIA for any hints,
Regards
DC