Developer Forum »
Reinstall large database
Reply to thread
58 posts
Reply Quote
Lars Erik Bjørn
04.06.2014  10.14

After having replaced a large database (5m+ rows, 4gb), I get no response from the WAFEngine. It just times out and just won't start up. I've set the HttpRuntime timout to 18000 which should be more than enough. Should I just increase it more, or are there any tricks to get this baby up and running again.

This is on localhost, and I've tried changing the wb.config, and I can successfully test the db connection from the setup-page.

120 posts
Reply Quote
Ole Gulbrandsen
05.06.2014  03.34

If this problem is some sort of timeout due the size of the database, try this:

  • Make sure the first request to the site is at a page that does not load a lot of objects, use "/edit" for instance.
  • Use MS SQL server, it is faster than MySql on larger databases. 
  • Make sure the SQL server has plenty of memory available and preferably a SSD disk.
  • Try with an empty database, to see if that makes a difference.

If the underlying problem is somethings else, examine if there are integrations in the solution that requires internet connections that might not be accessible from your dev machine. Examples: RSS feeds, serverside http calls, external Webservices, REST APIs etc.

58 posts
Reply Quote
Lars Erik Bjørn
05.06.2014  04.45

Empty db works just fine (which I kind of had guessed).Do I just have to set a really long timeout for this to finish?

 

58 posts
Reply Quote
Lars Erik Bjørn
05.06.2014  05.28

Well.. guess what.. after connecting to the empty db and then back to the old one, it just worked....? any clues as to why this helped? Nice to know if others experience the same problem. :)

120 posts
Reply Quote
Ole Gulbrandsen
05.06.2014  07.05

No, not sure what's going on here...

If it is repeatable, we would like to debug it.

Has anyone else seen this? Or have you had the same problem with other projects?

Ole

58 posts
Reply Quote
Lars Erik Bjørn
05.06.2014  07.12

I've had this problem before but it always resolved itself pretty quick so I just blamed it on the large database. I will let you know if I run into it again!

1