Hacker News Reader

Comment by Sammi | Hacker News Reader

You probably need to add some visual indicator that the generation is ongoing. A progress bar is ideal, but those can be hard to feed with real data.

View on HN

Thanks! I wanted to implement something like that, but it's difficult to predict the progress since it's depending on how many requests are being handled in that exact moment, but it never got past 25 minutes, not even during peak hours. I am thinking of adding a modal saying that you can close the page and you will get notified over email when the photo generation is ready (the email part is already there).

Doesn't have to be accurate. Just always set it to 30mins if it will never go past that. Most people will be pleased it finished sooner.

Maybe a queue then?

I am not sure if this is a problem that should prompt an architecture change of that caliber. I use a distributed network of GPU-machines and each request is handled sequential. If all machines are busy, then the request goes into a queue already and is being picked up by the first machine that becomes available.

Also, the user got the pictures after just a few minutes and there is a clear disclaimer, and an email is being sent to the user once the pics are ready. On top of that, I have no complaints from other users about it. It's clear to me that the intent of the user was to cause some reputation harm, which I think didn't work. I also got an email from a person with the same first name (not sure if it's the same person tho) that they offer UX services for Headsnap.

Reply on news.ycombinator.com