Live data from Hacker News

Ask HN: I built a site that just went ridiculously viral. What do I do now?

news.ycombinator.com

121–130 of 195 posts

Re: Ask HN: I built a site that just went ridiculously viral. What do I do now?

#123
Seems like a good place to ask this:

are those 'sign in with Facebook' buttons trust-worthy?

I've only clicked one of them, and that was a 'sign-up' button for an event i will be physically attending

everytime i see one, I worry that

a) it's going to broadcast to my entire friendlist that i signed up for this service

b) it's not a REAL facebook button, but something to phish my account

c) this site will know my Facebook login

d) some other party will intercept the login...

tell me it's completely safe?

Re: Ask HN: I built a site that just went ridiculously viral. What do I do now?

#125

That's why I use google appengine. It would have handled what you describe without even going over the daily free limit. Of course, you wouldn't be cool as rails.

You could be cool as Clojure, though: https://github.com/gcv/appengine-magic

Re: Ask HN: I built a site that just went ridiculously viral. What do I do now?

#126
Congrats on the App.

Regarding the BizModel. Forget it and grow as long as the hype works.

If you can't: Offer the possibility to add an optional reponse email. An ask for a penny if people want to contact the anonymous poster. Cooperate with FB for FB Credits to see this work.

Expansion: Threewords for all type of content (blog articles, third parties like celebrities, etc)

Re: Ask HN: I built a site that just went ridiculously viral. What do I do now?

#128
post #78
post #57

Where is your current bottleneck? mysql? check your slow query log, turn on the log-queries-not-using-indexes, do a quick analysis of those to see if you have queries that aren't using an index or queries that can be optimized. Probably 90% of the scaling problems are database issues. The quick solution is to scale up your current linode package, however, I think you might find that your traffic is going to peak and…

Last week I optimized some MySQL queries which triggered the 'not-using-index' warning, even when I had all fields which were used for selecting and sorting indexed. I think a JOIN on a nested subselect somehow confused MySQL: when I duplicated some extra restraining WHERE clauses into the subselect, response shot up from 800msec to 12msec per query. Very nice. But the query still shows up as 'not-using-index', which…

Very nice improvements. If you haven't already gone through these multiple times, I literally soaked in these last night:

http://www.slideshare.net/techdude/how-to-kill-mysql-perform...

http://forge.mysql.com/wiki/Top10SQLPerformanceTips

Good sets of additional tips/things to keep an eye out for.

Re: Ask HN: I built a site that just went ridiculously viral. What do I do now?

#129
post #78
post #57

Where is your current bottleneck? mysql? check your slow query log, turn on the log-queries-not-using-indexes, do a quick analysis of those to see if you have queries that aren't using an index or queries that can be optimized. Probably 90% of the scaling problems are database issues. The quick solution is to scale up your current linode package, however, I think you might find that your traffic is going to peak and…

Last week I optimized some MySQL queries which triggered the 'not-using-index' warning, even when I had all fields which were used for selecting and sorting indexed. I think a JOIN on a nested subselect somehow confused MySQL: when I duplicated some extra restraining WHERE clauses into the subselect, response shot up from 800msec to 12msec per query. Very nice. But the query still shows up as 'not-using-index', which…

Sometimes when you have complex queries it can make sense to create a temp table, create indexes on that, and then query off of that. But queries like that should show up in reporting, not in serving live web pages.

That said, if you're selecting more than 5% or so of the rows in a table, you're probably better off not using an index.

Another random tip. There is a world of difference between putting indexes on 2 fields, and putting a composite index on 2 fields. If you have restrictive conditions on 2 fields, MySQL has to work with the entire list of rows that match at least one of those conditions. (I don't know whether MySQL has the trick of joining indexes together before looking at rows, but even if it does it has to work with a list of rows matching the condition.) By contrast with a composite index MySQL can only look at rows that match both conditions. Much more efficient.

Re: Ask HN: I built a site that just went ridiculously viral. What do I do now?

#130
post #75

Why did you build it? What was your motivation? I tried it, and I have no idea why would I spam my friends with link so they would describe me. I have absolutely no interest in that, and I would feel really stupid sending anyone link like that. Did you actually felt the need to have such a website? Or you just figured people will like it? How did you figure that out? Please, share.

Teenagers are always looking for services like this one.
Post reply on HN