Earlier quoted context omitted.
Yearly revenue is $818,600 profit round $500k which is very nice but if "makes" in the title means "makes profit" as I assumed then the numbers are not correct. Profit of 500k / 12 = 41.7k per month, not 125k.
It is growing fast - avg of last 3 months is $125k. Yes it is revenue, not profit
Park.io – automating tasks to make $125k per month
71–80 of 210 posts
Re: Park.io – automating tasks to make $125k per month
#72Re: Park.io – automating tasks to make $125k per month
#73Jealousy and cognitive dissonance. This guy is more successful than them, so clearly he's done something bad. Welcome to HN: home of the insecure narcissists who like to argue over programming languages, humblebrag about their gifted childhoods, and prove that they're superior to anyone more successful than them.
We detached this comment from https://news.ycombinator.com/item?id=12576182 and marked it off-topic.
Re: Park.io – automating tasks to make $125k per month
#74I don't understand some of the negative comments here. This guy built a million dollar business in a year providing a service that people want to pay for. He did it all on his own with no other co-founders or employees. I say "Congrats!"
This hasn't happened to me, but it would be pretty crappy to find out you lost your domain because the script that your domain registrant uses to renew your domain name is slower than park.io's script.
Once your domain has expired, it will be in Auto-Renew Grace Period (for 0-45 days), followed by a 30-day Redemption Grace Period. At the end of the Redemption Grace Period, you will not be able to renew your domain name. Your domain name will be released for registration by third parties.
https://www.icann.org/resources/pages/expired-2013-05-03-en
For example, daily.sh will be available on their platform on 2016-09-30, but it actually expired back in 2016-07-01.
Re: Park.io – automating tasks to make $125k per month
#75Domain squatting as a service.
Re: Park.io – automating tasks to make $125k per month
#76Re: Park.io – automating tasks to make $125k per month
#77Jealousy and cognitive dissonance. This guy is more successful than them, so clearly he's done something bad. Welcome to HN: home of the insecure narcissists who like to argue over programming languages, humblebrag about their gifted childhoods, and prove that they're superior to anyone more successful than them.
I agree with you on the prevalence of envy in human nature (the real "hn" at work here), but using this community to diss the rest of the community is reliably a marker of a bad comment on Hacker News. Picking "humblebragging" and "prove that they're superior" as the points of dissage seems extra ironic. We detached this comment from https://news.ycombinator.com/item?id=12576182 and marked it off-topic.
Re: Park.io – automating tasks to make $125k per month
#78Re: Park.io – automating tasks to make $125k per month
#79Earlier quoted context omitted.
Yeah you usually need to warm it up if you're about to expect a lot of traffic because it can't really deal with that. That really shouldn't be an issue for a site like this though, because you can just host it on a CDN...
Top of HN traffic peaks at maybe 50-100 visitors per second. Unless you're serving a bunch of data, it really shouldn't be an issue. One problem I've run into is (I suspect) running out of sockets because they weren't getting recycled fast enough. This went away when I switched to Snap or Happstack. I used to have to "fix" this by killing and restarting my server every five minutes.
But if you're not getting recycling of TIME_WAIT, you can start to change the reuse/recycle attributes (caveat emptor) with: net.ipv4.tcp_tw_reuse or net.ipv4.tcp_tw_recycle
I know I have been benchmarking a servant app by throwing 2048 concurrent connections at it and just bumping up the ephemeral range has been enough for my needs.
I tend to run out of socket FD's or just FD issues a lot quicker than ports.
Just a thought, but 50-100requests/second doesn't sound like too big of a deal. I did a quick bench of what i have setup and I get this:
# wrk --latency -c 128 -t6 http://10.0.2.15:8080/foo/bar/
Running 10s test @ http://10.0.2.15:8080/foo/bar/
6 threads and 128 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 3.46ms 5.25ms 137.42ms 90.23%
Req/Sec 9.84k 2.13k 19.67k 69.50%
Latency Distribution
50% 1.65ms
75% 4.40ms
90% 8.59ms
99% 22.17ms
589624 requests in 10.07s, 476.28MB read
Requests/sec: 58560.86
Transfer/sec: 47.30MB
Note, this is a static end point so take all these figures with blocks of salt. But by tuning what I said I can have wrk do 2048 concurrent connections reasonably with just a fair increase in overall latency. YMMVRe: Park.io – automating tasks to make $125k per month
#80I don't understand some of the negative comments here. This guy built a million dollar business in a year providing a service that people want to pay for. He did it all on his own with no other co-founders or employees. I say "Congrats!"