There are of course dos and donts in Pike as well, but we try to adress them in the optimizer when we find them. But some tips are general and applicable
- Improve the algoritm One can not emphesize the importance of good algorithms enough.
- Trust nobody What was a really clever trick in one version in Pike may turn out to be slower than the naive way of doing it in a later Pike release (because the naive way has been optimized...)
- Avoid exceptions Exceptions are to be used in exceptional circumstances. In a way it is good that there isn't a good exception system in Pike, so that people writes code that more easily can be analyzed by humans and optimizers.
- Cache results Always possible, if you have more memory than time.
/ Martin Nilsson (Åskblod)
Previous text:
2003-01-28 20:09: Subject: reasons why pike is better than python?
hi,
someone posted this url: http://trific.ath.cx/resources/python/optimization/ in roxenchat with the comment that pike should have similar comments to help people optimize their code.
to me this page much more reads like a list of reasons not to use pike.
could someone please assert that pike doesn't have issues like these?
of course some optimization suggestions pointing out what things are in fact slow would be nice too.
greetings, martin.
/ Brevbäraren