Yeah with this categorization I agree with you!
the difference can be seen in this
Quote:
|
Like 32-bit threads, 64-bit threads also have a default of 1MB reserved for stack, but 64-bit processes have a much larger user-mode address space (8TB), so address space shouldn¡¯t be an issue when it comes to creating large numbers of threads. Resident available memory is obviously still a potential limiter, though. The 64-bit version of Testlimit (Testlimit64.exe) was able to create around 6,600 threads with and without the ¨Cn switch on the 256MB 64-bit Windows XP system, the same number that the 32-bit version created, because it also hit the resident available memory limit. However, on a system with 2GB of RAM, Testlimit64 was able to create only 55,000 threads, far below the number it should have been able to if resident available memory was the limiter (2GB/24K = 89,000):
|
In the case of 'jump' emerges that the problem is a possible Deadlock and he should test and profile is code.
For Deadlock can be used
Multi-Threading: Deadlock Tracer Utility
downloadable here
http://www.codeproject.com/KB/threads/MultiThreading_Dead_Lock.aspx
Regards,
Evilcry