C#/.NET Threading

[bluedes]

yaw mo pag-away oi..

How do you know it works slow when you still haven't tried it yet? There are alot of issues that slows down a thread.

sorry bro, but not a fan of .Net.. although that C# is a very powerful language, its sad na microsoft ang implementation ana..

.Net by itself is slooooowwwww... iyang overhead lng daan, sus paragaba.. bitaw, di man ko microsoft hater.. pero microslow jud na daan.. samot na inig threads ana..


anyway, tracelog is fine.. pero kapoy ko suwat ug logging callbacks gud.. unless sweto na kaau ka sa imong mga assert functions diha, pwede man na nimo gamiton as logging ba.. im sure .Net has its own logging facility.. pero hagbay ra ko nibiya anang .Net gud..

pero masganahan japon ko ug debugging, kay real-time man gud.. bantay lang na imong mga breaks dha dili mu-break sa uban threads..

[deadfinggerz]

pwede pud Print Debugging.. just print(sa console) what you want to know.. Gi gamit na xa sa mga maayo ug mga novice programmer.. simple ra kaayo just one line of code.. hehehe

[MarkCuering]

as soon as you triggered the start() method, your thread enters RUNNING STATE from UNSTARTED STATE, and it will continually running

There is no way to stop it like breakpoints not unless you will explicitly call Sleep() with maximum time that could give you chance to investigate. You cannot put a thread into ABORT/FINISH STATE, coz there's no way you could make it back to RUNNING STATE.

The only thing I hope is the release of Intel's Studio for the support of .NET/C#, and I hope they will shift this freely in our office, because it only support Unmanaged C++ so far...

you can checked it here -> Intel Software Development Products for Windows* - Intel® Software Network there is an Intel Thread Checker 3.1 and Intel Thread Profiler, this is what we are currently using.

I was looking something like this, in .NET Framework, but what they introduced is another API for CLR.

I was about to asked this also, but I found on gaston post here .NET Support - Intel® Software Network last nov. 19.
by the way, gaston is an author of this wonderful book Professional Parallel Programming with C#: Amazon.co.uk: Gaston C. Hillar: Books the author itself says that it is terribly difficult to handle threading in .NET Framework,

But don't close your doors of what you had previously think about .NET Threading. If you heard about Intel and Microsoft collaboration you will amaze. Intel is supporting its multi-core for .NET; this is how great Microsoft is when it comes to marketing. Check this out: Running .NET on Intel® Xeon® processors: The Fastest Platform in Town - Intel® Software Network

from the site:

the Xeon® processors' technological improvements come to the fore when running .NET appli cations on Windows servers. However, for the most part, .NET developers need not take any specific action to optimize their applications for the hardware, because Intel is working with Microsoft to build Xeon-processor-specific optimizations into the Windows .NET operating-system kernel and into the code for the Common Language Runtime managed execution environment.

[bluedes]

as soon as you triggered the start() method, your thread enters RUNNING STATE from UNSTARTED STATE, and it will continually running

There is no way to stop it like breakpoints not unless you will explicitly call Sleep() with maximum time that could give you chance to investigate. You cannot put a thread into ABORT/FINISH STATE, coz there's no way you could make it back to RUNNING STATE.

The only thing I hope is the release of Intel's Studio for the support of .NET/C#, and I hope they will shift this freely in our office, because it only support Unmanaged C++ so far...

you can checked it here -> Intel Software Development Products for Windows* - Intel® Software Network there is an Intel Thread Checker 3.1 and Intel Thread Profiler, this is what we are currently using.

I was looking something like this, in .NET Framework, but what they introduced is another API for CLR.

I was about to asked this also, but I found on gaston post here .NET Support - Intel® Software Network last nov. 19.
by the way, gaston is an author of this wonderful book Professional Parallel Programming with C#: Amazon.co.uk: Gaston C. Hillar: Books the author itself says that it is terribly difficult to handle threading in .NET Framework,

But don't close your doors of what you had previously think about .NET Threading. If you heard about Intel and Microsoft collaboration you will amaze. Intel is supporting its multi-core for .NET; this is how great Microsoft is when it comes to marketing. Check this out: Running .NET on Intel® Xeon® processors: The Fastest Platform in Town - Intel® Software Network

from the site:

the Xeon® processors' technological improvements come to the fore when running .NET appli cations on Windows servers. However, for the most part, .NET developers need not take any specific action to optimize their applications for the hardware, because Intel is working with Microsoft to build Xeon-processor-specific optimizations into the Windows .NET operating-system kernel and into the code for the Common Language Runtime managed execution environment.

ahh sorry, pero in pthreads, pwede man gud nimo ma-break ang individual threads..

di tingale pwede sa imo .Net, pero wa pa man sab ko katry jud ug threading sa .Net gud..

kung di pwede, aww tracelog ra jud ka ana..

[bluedes]

you can checked it here -> Intel Software Development Products for Windows* - Intel® Software Network there is an Intel Thread Checker 3.1 and Intel Thread Profiler, this is what we are currently using.

expensive software..

i'm not into expensive software for programming.. i left that industry a long time ago.. i'm into open source developments na karon.. layo na kaayo ko sa akong point of origin..

unsa diay imo work bro?

[MarkCuering]

If you still haven't tried and tested, better not to condemn it that it is slow but for the record, I find it slow hehehe…

[bluedes]

If you still haven't tried and tested, better not to condemn it that it is slow but for the record, I find it slow hehehe…

i've tried .net bro..

and compared to compiled C/C++, layo ra kaayo ang performance sa bytecode interpreted sa .Net.. i'm not condemning it.. that's reality.. pero i don't decline projects in C#.. basta kwarta na gani.. hehehe..