| Ramine <ramine@1.1>: May 22 07:35PM -0700 Hello... In this post i will talk about an important subject that is software "reliability", you have seen me on my previous posts explaining to you what is that it's efficient and reliable with my efficient Threadpool engine, and you have seen me talking to you about the automaton of my efficient Threadpool engine , this automaton takes care of software "reliability", like in design by contracts that takes care of realiability, i have finally been able to render my efficient Threadpool engine a reliable software by using an automaton that "guides" you by helping you to avoid forbiden transitions that can cause problems like deadlocks and dangerous problems, my automaton has made my efficient threadpool engine a reliable software, i explain more: since i am using 3 methods called execute() that distributes the jobs to the worker threads and i am using also setCounter() method with a boolean as a parameter and using also wait() method that waits for the jobs to finish (this look like a join()) with two parameters, but what i have noticed is that you can call those methods by combining them in a different ways , but this can cause some combinations that are forbidden to be called and that can cause deadlock or dangerous problems, this is why i have wrote an automaton that help you and guide you by using also exception handling to use the right combinations of those methods and there parameters, so like in design by contracts, my automaton has made my efficient Threadpool engine a reliable software. You can download my new efficient Threadpool engine version 2.01 from: https://sites.google.com/site/aminer68/threadpool-with-priorities Thank you, Amine Moulay Ramdane. |
| bleachbot <bleachbot@httrack.com>: May 23 12:35AM +0200 |
| bleachbot <bleachbot@httrack.com>: May 23 12:51AM +0200 |
| bleachbot <bleachbot@httrack.com>: May 23 01:34AM +0200 |
| Ramine <ramine@1.1>: May 22 06:54PM -0700 Hello, I have stress tested my scalable AMLock and scalable MLock(they are scalable Locks) and i have noticed by stress testing them that they are still causing a kind of deadlock, this problem is showing when you are using an asm pause instruction in place of a windows sleep(0) or a Linux Threadswitch(), this problem is showing on Ticketspinlock also , and becareful of the the proportional ticketpinslock that contains this problem, so i have corrected this problem and my scalable AMLock and scalable MLock are working perfectly now.. so i have updated all my projects to use my new scalable AMLock and my scalable MLock, please download again all my projects they are still at the same version even if i have updated them with the new scalable AMLock and the new scalable MLock. I have corrected also this problem on my efficient Threadpool engine, so finally i think all my projects are reliable and stable and fast. So be happy with them ! You can download again all my projects with the new update, they are still at the same version except for my efficient Threadpool engine that i have just updated to version 2.01, you can download them again from here: https://sites.google.com/site/aminer68/ Thank you, Amine Moulay Ramdane. |
| Ramine <ramine@1.1>: May 22 06:38PM -0700 Hello, My efficient Threadpool engine was updated to version 2.01, i have analysed the automaton of my Threadpool engine and i have noticed that it was still allowing some forbidden transitions, so i have added more to the automaton so that it forbid all the forbidden transitions, and i think now that it is more efficient and reliable. So hope that you will be happy with the new version 2.01. You can download my new Efficient Threadpool engine version 2.01 from: https://sites.google.com/site/aminer68/threadpool-with-priorities Thank you, Amine Moulay Ramdane. |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.programming.threads+unsubscribe@googlegroups.com. |
No comments:
Post a Comment