Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
baruch
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
18 ms
·
151.
▲
by
baruch
11y ago
F2FS is for direct NAND access, if you do it over an SSD that already has an FTL (flash translation layer) you'll gain nothing and only cost extra writes.
152.
▲
by
baruch
11y ago
I would argue that preferring to reuse the same space of the SSD instead of using new space as you propose (cow, et al.) is the better approach. This way you don't need to use trim that much and the SSD will anyway write it into a diff
153.
▲
by
baruch
11y ago
The browser cache is about caching network resources and not about ram, pages you visited yesterday are cached there and will have no place in ram.
154.
▲
by
baruch
11y ago
These devices do not expose their inner SSD and only utilize it as a cache. You are probably better off with an SSD standalone or with a full blown SSD as a block cache to the HDD in part and as a direct drive in the other part.
155.
▲
by
baruch
11y ago
I wouldn't bother with any of this. The effects on the SSD are too low to be worth it and there is no discussion on the tradeoffs that are being taken. Disabling hibernation is really a shame for one. Trim is done excessively and the b
156.
▲
by
baruch
11y ago
Brothers in Exile: Sons of the Starfarers by Joe Vasicek Was a free book on my new Kobo Touch, bought the next two books in that series and now in the middle of the second book. Nice plot and writing.
157.
▲
by
baruch
11y ago
The spec is for the worst performance possible at end-of-life time. So a new drive will retain the data far longer than 3 months or 1 year of the spec (enterprise vs consumer spec) but a drive after five years of full writes will retain for
158.
▲
by
baruch
11y ago
The requirements for an enterprise SSD is lower than that of the consumer SSD under the assumption that such SSDs are hardly ever left unpowered for an extended period of time. The SSD is in fact better because it better uses its internal r
159.
▲
by
baruch
11y ago
The paper took something out of context, didn't really understand what it reads and published nonsense. The original blog post linked from the article is https://blog.korelogic.com/blog/2015/03/24#ssds-ev
160.
▲
by
baruch
11y ago
At the simple side of things you can write your own implementation and use known test vectors to verify that your implementation is acting the same as other implementations. That should cover interoperability. Some of the issues in cryptogr
161.
▲
by
baruch
11y ago
There was a similar issue in the Linux kernel in version 2.6.32 where the kernel would crash after 208 days: http://www.novell.com/support/kb/doc.php?id=7009834 This was a serious problem in some storage systems t
162.
▲
by
baruch
11y ago
Unless you are optimizing for a specific SSD with known quantities there is no real way to do that. The high-level optimizations are important: * Choose a good SSD * Read and Write in "page" multiples and "page" aligned
163.
▲
by
baruch
11y ago
Indeed :-) If you really want to be pedantic, there are electrons moving in there so it is solid state but it has moving parts :-)
164.
▲
by
baruch
11y ago
I've had that much acknowledged from SSD vendors, each one blames the others for the benchmark wars but they all know that benchmarks are out there and customers will chose the SSD based on the published benchmarks so they tune the fir
165.
▲
by
baruch
11y ago
SSDs live off their internal parallelism, if you aren't using a Queue>16 you are not making real use of an SSD. Q=32 or even Q=64 are usually the right settings. It all depends though if you want throughput or latency. If you really
166.
▲
by
baruch
11y ago
There is unfortunately no good place to do that. I work in an enterprise setting and get to talk to the ssd vendors and fish for details on how to best use their ssds and I still find it hard to get full information. Sometimes I wonder if t
167.
▲
by
baruch
12y ago
If a mainboard fails you replace it and get back up (with downtime), if an SSD fails you lost your data. If you care about your data put some redundancy in it. Even for the case that a motherboard fails having redundancy will help with the
168.
▲
by
baruch
12y ago
The 15k HDDs will likely be replaced by SSDs, the 7200 ones are likely to stay for a long while yet. Their capacity is yet unmatched, the SSDs are trying to catch up with higher densities but currently the HDDs are ahead of them on the curv
169.
▲
by
baruch
12y ago
I would strongly recommend also testing for when things fail. This is the hardest part in troubleshooting and building a reliable system. You can make do with READ/WRITE LONG if the disks are SAS to generate medium errors, be aware tha
170.
▲
by
baruch
12y ago
But these details do matter when you want to achieve maximum performance and they also matter when you want to figure out what went wrong with the device when it fails. The hiding the happens currently in the block interfaces (HDD, SSD &
171.
▲
by
baruch
12y ago
It's hard to come up with evidence since there are very few options to create your own SSD/NVMe firmware for a real-world like device. The closest I've come up with is OpenSSD and that required $3000 and was for an old contro
172.
▲
by
baruch
12y ago
Presumably you'd run one application inside such an image and between two images you do have isolation.
173.
▲
by
baruch
12y ago
But it's not just process isolation. You also isolate the entire OS, so you can tune your TCP stack to match this application without affecting the others. If you go deeper than that you can even give access to the hardware and thus re
174.
▲
by
baruch
12y ago
I've used redo for a while but I didn't like the sprawl of shell script files for the build to work. I switched to ninja mostly for more complex projects and it's very nice, you can do anything in the generation stage and get
175.
▲
by
baruch
12y ago
I've never seen such an incompetent person hired anywhere I worked for. I did see similarly qualified people turn up to interviews but they were all invariably rejected.
176.
▲
by
baruch
12y ago
I simply use Debian in unstable all the time and update every couple of weeks. I hate staying stuck for a year or more with old versions and unstable was very rarely unstable for me. There was once or twice in the 10 years or so that I'
177.
▲
by
baruch
12y ago
This guide needs a part on "How an SSD fails" and explanations on what to expect from SSD failures and especially the soft-errors that may occur. I also can't stress enough that SSDs are born for multi-threaded. If you aren&#
178.
▲
by
baruch
12y ago
Any newer TCP is more aggressive than Reno. Reno is very slow, that's why everyone tries to find a new algorithm that is far more aggressive in order to utilize the bandwidth and still be fair towards other TCP algorithms. Since TCP is
179.
▲
by
baruch
12y ago
I use a similar tool (pwdhash) and the benefit is not that it's a single password but a single root password. I need only a few changes and very little to remember for most sites and still get a unique password per site. My bank requir
180.
▲
by
baruch
12y ago
If there was an option to take an existing high volume product and get the tools and interface documentation to create and modify the firmware for I'd jump on that bandwagon as well. So far I didn't find anything like that.
More ›