Improve "busy" numeric code's performance [was: Re: Big Integers]

2024-05-22 Thread Peter Bex
Hello Doug and CHICKEN hackers, Thanks for the benchmarking program. Somehow your e-mail is a bit garbled, hence the top-posting, for which I apologize. The benchmark in question deals mostly with small-sized bignums, which means we're not even trigger the fancier division algorithms. This is a

Re: Improve "busy" numeric code's performance [was: Re: Big Integers]

2024-05-22 Thread Peter Bex
On Wed, May 22, 2024 at 02:42:38PM +0200, Peter Bex wrote: > Attached are two patches, one which has this bigger improvement, and > another which is a minor improvement which translates to shaving about > a second of runtime off your program (at least on my machine). The minor patch was incorrect.

Re: Improve "busy" numeric code's performance [was: Re: Big Integers]

2024-05-22 Thread felix . winkelmann
> On Wed, May 22, 2024 at 02:42:38PM +0200, Peter Bex wrote: > > Attached are two patches, one which has this bigger improvement, and > > another which is a minor improvement which translates to shaving about > > a second of runtime off your program (at least on my machine). > > The minor patch was

Re: Improve "busy" numeric code's performance [was: Re: Big Integers]

2024-05-22 Thread T.D. Telford
With patch 0001 the elapsed time went from 33.7 seconds to 24.5 seconds. With patch 0002 the elapsed time went to 23.4 seconds. Good work -- Doug On Wednesday, May 22, 2024 at 08:54:49 AM MDT, Peter Bex wrote: On Wed, May 22, 2024 at 02:42:38PM +0200, Peter Bex wrote: > Attached are two