194 karma · joined September 30, 2014
We ended up with the realization that the rental housing stock in the Bay Area are all very old, usually not well maintained and depending on the area, very likely to have or have had water damage, the only thing we could do to get into newly built housing, was to rent an apartment.
The amount of bad information and advise is pretty staggering – if you're adversely reacting to the environment you're in, the best thing you can do is remove yourself from it, then accept that you may never be able to return to it.
Anyway, this all sounds very familiar and you're welcome to reach out to me at <hn-name>@icloud.com – and that goes for anyone else dealing with similar stuff.
Edit: missed an s in dessert.
Allowing every site access to quietly scan for devices would be pretty horrible, but that's not the case from my understanding.
Well worth a watch of you're unfamiliar with the project.
Any advice for people going though a very tough time you'd like to share?
It was a complete nightmare unless you understood what public key crypto is, how it works, and how to configure your browser for it.
Don't get me started about having to move your certificate/keys around.
It doesn't work for the masses.
What a strange choice by the Linux kernel.
Sums it up pretty good.
You should look into dtrace and it's new Linux counterpart who's name currently alludes me. It's almost like being able to do just that.
Back then fbsd had something called accept filters, which basically made the accept call only return when a http request was received in the network buffers.
Systems running fbsd loaded up different than Linux, kept being responsive. On same hardware, could do 3-5x more rps with lower load iirc.
As my applications at the time became more cpu bound, I switched to Debian around 4.11.
I've recently been using 10.x, coming back to fbsd from 10 years of Debian. I love what you've done while I was gone. Especially binary packages and easy upgrades, but especially jails and zfs.
http://webcache.googleusercontent.com/search?q=cache:http://...
I'm sure neither should be used in a production project.
[1]: https://github.com/snoack/python-goto/blob/master/goto.py
If anything, think, just for a second, how much this law has costed the EU, and how many hours has been wasted reading/participating in the law. Of course, it could be one way of stimulating the economy, but I'd like to think it wasn't.
If you know of any tools like gor, I'd very much like to know of them.
Gor does packet capturing and duplicates the requests to any number of environments.
It's a different tool for a different task.
Github will probably have more downtime which you can do noting about, than your selfhosted gitlab, which will probably fail because you upgraded something, or tinkered with a configuration.
It's a numbers game. They have more people monitoring, they spend way more money than you do on uptime/services, but such a service doesn't get more stable as it grows.
I trust myself way more than I trust GitHub or other hosted/cloud services because I cannot affect/help them in any way when stuff happens.
Ultimately, I know this, I accept this, and I happily use GitHub, Bitbucket and such all the time.
That and OS/2.
> Each server has access to a pool of local drives. These drives are exported to servers via the NBD protocol which effectively makes them network drives. However, network between these drives and C1 nodes are dedicated PCB tracks which ensures minimal latency and avoids network congestion.
> There is no redundancy on these volumes, you need to handle redundancy on your side! They are archieved to a permanent storage when you start and stop your server.
> Local volumes are 100% SSD drives which are able to deliver a lot of IOPS and are perfect for random read/write patterns. The maximum size of LSSD volumes is 150GB.
xnbd-client --blocksize 4096 --retry=900 10.1.32.197 4096 /dev/nbd0
root@scw-6d2eff:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nbd0 46G 507M 44G 2% /
I did not check, but I hope there's some filtering/authentication for that process.Like EC2 and others, the box has an internal ip allocated and an external ip via nat (or something else).
I was able to download a file from OVH with ~500 Mbit/s throughput when writing to the filesystem. Writing to /dev/null it increases to ~650 Mbit/s.
Running an untuned nginx, it can do ~300 req/s with ~20% cpu util.
Seeing as the storage is still virtual, I'm not really sure why this would be so much better than a virtual machine. I like the idea though.