OpenEuphoria

Re: Missing messages

• Posted by Robert Craig <rds at RapidEuphoria.com> Dec 17, 2005
• 519 views

Vincent wrote:
> Robert Craig wrote:
> > In a nutshell: 
> >    Topica = unreliable (messages delayed, out of order, sometimes lost)
> >    RDS EUforum Web interface post/view messages = reliable
> >    RSS feed = reliable (if you check it daily)
> 
> How come you chose Topica anyway?

Chris Bensler set it up. 
It was free.
It was better than Yahoo or MSN groups.
We needed a moderated group since someone was causing
problems and we had no way to control what he posted or
how often. We had kind of overstayed our welcome on 
a university server that we had little control over,
and which had no decent moderation facility.

Lately Topica has deteriorated a bit more.
I recommend that people consider RSS or simply
use the RDS web interface.
 
> BTW... Where you able to pinpoint the issue with sequence operations or you
> still trying to figure it out? That might be a good program to include with
> modern Euphoria distrobutions and for your personal testing. I would test
> again
> when you build Euphoria with Open Watcom v1.4 with better compiler optioned.

Yes, I figured it out.
2.5 ex.exe is actually faster than 1.2 ex.exe by about 20% when
doing sequence operations. Where 1.2 is winning big-time is
on the time() function. Each of these benchmarks 
calls time() each time around the loop. 1.2 uses the old
DOS4GW DOS extender that I think had a special optimization
for time(). Anyway it's about 70x faster than the time()
in 2.5. time() does a DOS interrupt, something that's often quite
expensive with a DOS extender. 

Note: With exw, time() is extremely fast.
Much faster even than ex version 1.2.

I checked 2.5, 2.4, 2.1, 1.4, 1.3 and 1.2. 
The change comes between 1.3 and 1.4.
That's when I switched to the CauseWay DOS extender.
2.5 comes out a bit faster than all the other releases
after 1.3 on this benchmark. I think the benchmark is 
a bit flawed because it inadvertantly places a lot of 
importance on the time() function.

Fortunately, when a program calls time(),
it's usually not in a time-critical section. 
Often it's just waiting for the clock to advance,
or it's timing some operation.

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com