Bhavesh, Go is great for big projects.
You don't say specifically which part is slow, nor which database you are using, so it is hard to give specific advice. You should measure and profile to see what part of your process is taking a long time. Go has great profiling tools. That's one of the reasons it is good for big projects. There are some standard tricks if, for example, your initial data load (say, alot of inserts) into an empty set of indexed tables is too slow. And this may mean going outside of an ORM and even outside of SQL. For example, you may then need to resort to the old standby of halting all reads, dropping all indexes--or here, not creating them in the first place, and then doing the equivalent of LOAD DATA LOCAL INFILE (specific to MariaDB; the idea is to read from local disk into database storage on local disk without transactional overhead), and then, only once that is done, applying or re-applying the indexes. Creating indexes in batch can be massively faster than updating them after each record is inserted. That's just one example. The details are... the important bit. You've left them out. Feel free to tell us more. Best wishes, Jason -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/02e2a1dd-1b35-4674-8e21-ec081889ffeen%40googlegroups.com.
