Hacker News Reader

Comment by mbien | Hacker News Reader

Perfectly understood! We just cannot afford to run it on GPU in the backend so the generation takes up to 3 minutes which is terrible thing to do interactively :( You're invited to check it with 10minutemail or so, or you can try our model on your own if you have some python experience: https://huggingface.co/mbien/recipenlg

View on HN

For privacy conscious and if you're willing to go that far[0], you can generate a unique URL for a recipe and store it for a limited amount of time. With that (and the URL being generated beforehand), you can tell the user to either provide an email address so you can email them, or just to visit the link later and check if the recipe is ready.

[0] Personally I wouldn't worry. It's open source and people can run it themselves if they're squeamish, and probably your time would be better spent on the engine itself :-)

If you don't mind me asking, how much does it cost per recipe(s) on CPU vs GPU?

I also wouldn't mind waiting 3 minutes if there was a direction telling me so, with a timer.

Hard to say per recipe, as in the current setup they are generated on demand and not pre-generated. But as you can see, we're hosting the solution in academia so it's basically for free vs around 2$/hour with GPU on AWS

Yes, you might be right about the timer, we'll think about changing it!

How about using browser notifications? That way, one could leave the website, receive a notification about data being ready, and click on it to find the generated recipe.

Reply on news.ycombinator.com