I ran my stack "OmniLotto" and generated 5000 random powerball games. Then
it ran. It .took over 30 minutes!!!
I saved the 5000 gamelist and ran it through my PERLotto perl script out to
"results.txt".
It took only 1 second!!!
What gives? Are my script routines way out of order? It certainly
>
> I ran my stack "OmniLotto" and generated 5000 random powerball games. Then
> it ran. It .took over 30 minutes!!!
>
> I saved the 5000 gamelist and ran it through my PERLotto perl
> script out to
> "results.txt".
>
> It took only 1 second!!!
>
> What gives? Are my script routines way out of
Dar Scott wrote:
On Tuesday, August 5, 2003, at 08:17 PM, Pierre Sahores wrote:
About console-mode apps : Rev and MC are exactly similar about the
high speed (lots faster than Java-based apps) they are able to handle
in running console-mode deamon apps.
I'd like to learn more of these.
Dar Sc
Woah guys, let's not bash the new guy quite so quickly.
I know we all love Revolution and don't like to hear that something
"sucks", but:
* He asked for advice, got it, and thanked everyone repeatedly for it
* He already posted the URL for his perl script
* He readily admits that the differenc
On Donnerstag, Aug 7, 2003, at 23:37 Europe/Zurich, Alex Rice wrote:
repeat for each line theLine in theWinners --note: NOT "each line
theLine in fld winners"
This is wrong. Actually when you do a "repeat for each" loop, then you
generate automatically a variable at the beginning of the loop and
On Thursday, August 7, 2003, at 04:03 PM, yoy wrote:
Alex,
Apoligy accepted.
I was hypercard since 1987
Well you actually have ~15 years more experience with xTalk than I do
:-) I found Rev last year and haven't looked back. Experience comes in
lots of paths and ways. Glad to have you with us
On Friday, August 8, 2003, at 12:16 AM, Dar Scott wrote:
put fld "winners" into theWinners
repeat for each line theLine in theWinners
I think what he is saying is that that is equivalent to this
repeat for each line theLine in fld "winners"
and that the compiler essentially does what you ha
Agreed. But that applies to any source code. I have had trouble reasoning
with my own source code after time passes.
Try reasoning with:
http://mywebpages.comcast.net/foxcat/GAUGE_88.ps
Use distiller to get the .pdf (font's may fault the reulsting file).
Today, I looked at that code and thought
On Tuesday, August 5, 2003, at 10:01 PM, Richard Gaskin wrote:
- Unless a lengthy operation also needs to process system messages, use
"lock messages" before the operation and "unlock messages" when it's
done.
Richard, the Rev docs mentions "lock messages" but not in the context
of optimization.
Geoff Canyon wrote:
> If the script I'm looking at is the one you're talking about, it's
> parsing through the contents of the field one bit at a time, and
> setting the style of text (text color) bit by bit.
>
> For speed, you need to get the contents of the field, work on that
> (paying special
and see how it behaves, tomorrow!
Regards,
Andy Burns
- Original Message -
From: "Geoff Canyon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 05, 2003 11:37 PM
Subject: Re: Revolution speed sucks?
> If the script I'm looking at is
I'm just getting back into the game. I like Revolution's rapid development
but have probably less time to learn than the trial allows.
All the best,
Andy Burns
- Original Message -
From: "Alex Rice" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursda
On Wednesday, August 7, 2002, at 02:29 PM, Brian Yennie wrote:
* He already posted the URL for his perl script
...
Oops, I apologize. It did not appear to me that he had posted the Perl
code for comparison. I re-read the thread and found that he had done
so. Sorry Andy! That URL is
http://mywe
Alex Rice wrote:
> On Saturday, August 9, 2003, at 07:06 PM, Scott Rossi wrote:
>
>>> The subject line bugs me. People do get protective of their favorite
>>> programming tools you know :-)
>>
>> A small request: let's not start a "no bashing the tool" movement.
>
> Fine by me, however if some
I also didn't mean to bash anyone back, if that's how it came across.
In any case, I just didn't want Andy to feel singled out or shot back
at.
Now that we've all kissed and made up, back to it!
Andy, I downloaded your Perl script and it's actually quite readable
for Perl (which is in fact a g
Amen!
BTW, I did indeed out of curiosity port the Perl code behind this
thread almost line-by-line into MetaTalk. The result? No matter how
hard I tried the Perl code ran at least 10% faster. Not a big
difference, but the MetaTalk was NOT a clear winner by any means.
That doesn't mean Perl is
From a first glance, these tips should buy you an initial speedup, and
are mostly GUI-related.
1) Don't read line-by-line through a field. Instead of:
repeat for each line gameLine in fld "gamelist"
do this:
put fld "gamelist" into gameList
repeat for each line gameLine in gameList
You also re
Andy, grab some coffee and lets chat.
On Thursday, August 7, 2003, at 12:29 PM, yoy wrote:
Still, Perl is much faster. I generated another 50,000 games
(Powerball) and
with error checking and print OUT and it took only 5 seconds.
The price you pay for a gui?? Maybe I just wrote better perl code
Alex Rice wrote: >
I don't want to be policed either.
(snip)
Agreed. Self-restraint through simple professionalism should be sufficient.
--
Richard Gaskin
Speed is great.
Self-restraint sucks. :-)
Jim
___
use-revolution mailing list
[EMAIL PROTECTE
On Wednesday, August 7, 2002, at 02:29 PM, Brian Yennie wrote:
* He asked for advice, got it, and thanked everyone repeatedly for it
* He already posted the URL for his perl script
* He readily admits that the difference may be that his perl script
was better written!
* He and several list mem
riginal Message -
From: "Richard Gaskin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 06, 2003 12:01 AM
Subject: Re: Revolution speed sucks?
> Geoff Canyon wrote:
>
> Even as-is, the Start button there executed its script in just a few
secon
Did your revolution script read in and write out to text files as the
PERLotto script does?
Yes. It uses your config file and writes out to "results.txt".
If so that may explain the 10% Perl speed advantage. Did you read in
and
write out to a field? Did you read the field into a variable and the
Alex Rice wrote:
> On Tuesday, August 5, 2003, at 10:01 PM, Richard Gaskin wrote:
>> - Unless a lengthy operation also needs to process system messages, use
>> "lock messages" before the operation and "unlock messages" when it's
>> done.
>
> Richard, the Rev docs mentions "lock messages" but not
On Friday, August 8, 2003, at 12:03 AM, Alex Rice wrote:
put fld "winners" into theWinners
repeat for each line theLine in theWinners
I think what he is saying is that that is equivalent to this
repeat for each line theLine in fld "winners"
and that the compiler essentially does what you hav
or many OSs and I really want to get gui
apps
out there for those who want my offerings.
There's so much to learn, again! ;-)
All the best,
Andy Burns
- Original Message -
From: "Brian Yennie" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, Aug
Brian Yennie wrote:
> The behavior is as close as possible to the Perl script, since I wanted
> a fair comparison of the engine alone: it reads from a file and writes
> to one in the same manner as the Perl script. It could be sped up by
> using variables and writing the file once, but then it wou
On Friday, August 8, 2003, at 12:36 AM, Alex Rice wrote:
But yes, since the speed is the same with both forms, it must be doing
what Björnke says- making a temporary var with the contents of the
field.
If that's the case then this opens up the opportunity to fiddle with
things in the limit expr
most curious and "sharing the magic" is never a bad thing, right?
;-)
Regards,
Andy
- Original Message -
From: "Brian Yennie" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, August 10, 2003 7:41 PM
Subject: Re: Revolution speed sucks?
> BTW,
On Tuesday, August 5, 2003, at 07:53 PM, Monte Goulding wrote:
Scripts that take a very long time generally do stuff like put
something
after a field in every repeat loop rather than build a variable then
display
at the end.
If I was a bettin' man, I'd bet on exactly that.
Maybe I'll but someth
Hi Andy,
I would guess you have run into a factor that is both a strength &
weakness of xTalks like Revolution: there are ALWAYS multiple ways of
doing things and some are much slower than others. If it is a one-off
routine, it really doesn't matter how you go, but in a frequently
repeated rou
Alex Rice wrote:
Also Perl is "write-only". Try reading your lotto script in 18 months
after finishing it!
This is just an ingenious way of bringing retribution on programmers
that do not write copious explanatory comments, and have a penchant for
deviously clever implementations. But I suspec
Richard,
I wrote it as a MetaTalk script: that is, no GUI. It writes the results
to a file. The main benefit that this ignores is the ability to
pre-compile the script (which stacks do every time you save a script).
When I pasted the same script into a button in the GUI (still no
display, just
On Thursday, August 7, 2003, at 12:29 PM, yoy wrote:
Still, Perl is much faster. I generated another 50,000 games
(Powerball) and
with error checking and print OUT and it took only 5 seconds.
The price you pay for a gui?? Maybe I just wrote better perl code than
revolution code. ;-)
Andy, look
Sarah,
Thanks for your speed.rev tester. It's very good.
My .rev stack lets a user config a 5 or 6 ball lotto with optional support
for bonus ball.
Usually the lotto will be a straight 6 ball lotto or a 5 ball and 1 bonus
pick. The problem is whether it's a straight 6 ball lotto or a 5 + 1 bonus
On Thursday, August 7, 2003, at 12:29 PM, yoy wrote:
The variable testing makes much sense. If the lotto were a Powerball
lotto,
I could grab the first 5 items and place them in one variable and put
the
sixth item into another variable, test the first variable of 5 numbers
using
for each, and t
If the script I'm looking at is the one you're talking about, it's
parsing through the contents of the field one bit at a time, and
setting the style of text (text color) bit by bit.
For speed, you need to get the contents of the field, work on that
(paying special attention to repeat for each)
On Tuesday, August 5, 2003, at 10:26 PM, yoy wrote:
Still, PERLotto is way faster, but I have some trial days left to work
it
out.
When all the no-nos are corrected, I would wager, the Rev version will
be faster :-)
Perl, although fast, does not have as sophisticated compilation as Rev.
I thi
While the interest in fairnes is appreciated, if you're using fields
instead
of variables it tilts away from Rev unfairly, as Perl has no rich-text
field
objects to contend with.
I'm not using fields at all: I'm writing directly to text files. I also
ran both in the script engine (no GUI at all)
Richard Gaskin writes:
Alex Rice wrote:
On Saturday, August 9, 2003, at 07:06 PM, Scott Rossi wrote:
The subject line bugs me. People do get protective of their favorite
programming tools you know :-)
A small request: let's not start a "no bashing the tool" movement.
Fine by me, however if s
On Saturday, August 9, 2003, at 07:06 PM, Scott Rossi wrote:
The subject line bugs me. People do get protective of their favorite
programming tools you know :-)
A small request: let's not start a "no bashing the tool" movement.
Fine by me, however if someone posts "this tool sucks and is slow", a
For my money, 10% lower speed is a small price to pay for the benefits of being able
to develop in an Xtalk (like, for example, I don't need to learn Perl).
The thing that I really like about Revolution is that I can learn 1 language and apply
it to nearly any kind of problem. It may not always
> Monte and others,
>
> My .rev stack is available at
> http://mywebpages.comcast.net/foxcat/OmniLotto.rev
>
> There are bugs in it so for best results go to the Prefs stack first and
> click the OK button then press the Start button on the mainstack.
> I'm still
> scratching my head on that issue
On Wednesday, August 6, 2003, at 03:32 AM, Pierre Sahores wrote:
Because the answers have to do with the OS the deamon apps are running
on, what are the platform's operating systems your are developing for
(MacOSX, Win32, Linux,...) ?
I want it all! Let's start with Win32 (or a subset) or OS X.
Dar Scott wrote:
On Wednesday, August 6, 2003, at 03:32 AM, Pierre Sahores wrote:
Because the answers have to do with the OS the deamon apps are running
on, what are the platform's operating systems your are developing for
(MacOSX, Win32, Linux,...) ?
I want it all! Let's start with Win32 (or
44 matches
Mail list logo
