Re:Web-app version of Markov-Chain domain generator (be gent...
by kwamenum86 on Saturday October 25, 2008 @10:46PM
(#343990)
Are you caching the results on your server? You should cache the results for a better response time. That way you can return more information to the browser without checking availability for the same queries over and over.
For example, save the availability of picklenickel.com for 24 hours (or maybe more I don't know). Then you can do some recursive calls using cached data. Making all those concurrent HTTP requests seems impractical and has to be affecting your server's responsiveness.
Re:Web-app version of Markov-Chain domain generator (be gent...
by codeismightier on Saturday October 25, 2008 @11:00PM
(#344005)
I am running a local resolver (bind9), so I would assume that it is being cached.
Re:Web-app version of Markov-Chain domain generator (be gent...
by kwamenum86 on Saturday October 25, 2008 @11:20PM
(#344018)
Hmm. It's strange the initial requests usually take 20+ s but the subsequent recursive requests take ~200 ms each. Maybe a bottleneck in the code?
Re:Web-app version of Markov-Chain domain generator (be gent...
by ojbyrne on Saturday October 25, 2008 @10:56PM
(#343999)
I can't actually see the site yet, so I'm totally guessing, but a better way to do ajax autocomplete type things is to use SetTimeout or SetInterval to poll, rather than onKeyDown.
The reason that the script issues a recursive call is that I want the user to see the suggestions right away and check the status later since the DNS requests can take a while.