SQ79@liverpool.ac.UK (Mark Powell) (08/23/89)
Maybe you should have a good look at your code. If you're program is
really _meant_ to take weeks/months to run then optimisation of the code
would probably be a better idea that buying yourself one of the many turbo
boards around. Even a simple change would reduce running time considerably,
if, say, you halved the clock time of a major routine that may be executed
millions (maybe billions) of times in a month, you'd be doing yourself a big
favour, time wise. Maybe, if you've got a lot of money, you could get a turbo
board as well. Try to get one that has a data cache as the _can_ be
considerably faster than those that don't. (I say "alot" but a 16Mhz board
with an 8K data cache can be bought for around 130 pounds... you want dollars
... well I don't know about that, but alot of info. about various turbo
boards was posted
If you do get a turbo board then, optimise your code _for_ the board.
i.e. try to keep values in registers rather than memory... if you have to use
memory then try to keep it small so it'll be cached every time you need to
use it etc.
If you desperatly need it faster then you could mail me the source, and I'll
have a look at optomising it for you. (don't tell me it's about 200K of
68000). You could mail it to the net, but that's not too nice on the pockets
of all those people getting news, at home, via modems.
Mark Powell
ARPAnet : sq79%liv.ac.uk@{ucl-cs.arpa,cs.ucl.ac.uk,NSFrelay.ac.uk}
USENET : ...!mcvax!ukc!liv.ac.uk!sq79