> I don't know much about your background so please forgive me if I give > you obvious advises, but perhaps you'd be better *first* coding the > solution to your problem - eventually looking for help on > comp.lang.python. Then you'll have real facts, not estimations. > Specially if yourcomputationhappens to be memory-hungry, since the > best way to put a server on it's knees is to make it go swapping. So > in your case, you may want to look for space optimisation instead of > time optimisation.
Well, yes, but I'm trying to decide what language to use to program this computation. Since my web framework is written entirely in Django, there's a bit of an advantage to using Python, just in terms of seamlessly calling the function from Django (but do I use separate threads, separate process, or do I not even need to worry about that?). But I can probably get a hundred-fold speedup by using a statically-typed, compiled language. But then I am forced to use a separate os process to call the program (more heavyweight than threads?), and need to find a language with an API to manipulate the database, worry about privileges, etc. That's why I'm asking now, ahead of programming, for more info about how hard it is to incorporate an intensive computation into the Django framework. It could very well affect my choice of language. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
