If you plan to create a batch of objects, I wouldn't recommend going that route. Instead, check this out:
https://docs.djangoproject.com/en/dev/howto/initial-data/ Has Django really such a bad performance for data insertion? The Object Relational Mapper does quite a bit more than simply write SQL insertion queries. I won't go into the details simply because I don't want to run you in the wrong direction but if you're interested in that topic, I'm sure someone else can fill you in on the details. However, the main bottleneck that I see is in the structure. If you expect 5,000 queries at once on a regular basis then you may want to structure your application around that. Or, at least the part that performs this batch insertion. Even a relational database management system will most likely have issues with performing that type of duty directly (without the Django layer) unless it's optimized and tuned correctly, sitting on extremely fast IO hardware, etc... Judging from your times with SQLite, I would guess that part of your problem is the IO performance (Hard Drive), since SQLite stores its data directly into a file. Not sure if this answers your question but hopefully it might lead you in the right direction :) Good luck! -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
