12 ms·
1) Build your app how you would normally build it (obviously dont expect to put massive objects into memory for every request — just dont worry about the small
by ashleyw 18y ago
1) Build your app how you would normally build it (obviously dont expect to put massive objects into memory for every request — just dont worry about the small things)
2) Go back and refactor the things that really stick out as bulky
3) Deploy
4) Continue your release cycles and refactor stuff as you come across them
.
As the saying goes — hardware is cheap, your time isn't.
- jamesbritt 18y ago"As the saying goes — hardware is cheap, your time isn't." Don' t many small companies find that they have more time than money?
- ashleyw 18y agoI guess, but that "extra hardware" wouldn't be that much. I was talking about like 1 second extra CPU time per 50 page loads or something — I wouldn't worry about that kind of thing, even if I had time to make my code slightly faster, I'm sure I could spend my time better. Maybe I'd refactor it later on when I'm adding extra functionality to that area of code. I think if your a small company you shouldn't be worrying about small issues like this, even if you have more time than money. It may be making your app more efficient, but your doing it the same way people make apps bulky and never get them out the door! Spend the time on things which truly matter, and fix slightly slower code when its beginning to cause a problem. :)