HackerTrans
トップ新着トレンドコメント過去質問紹介求人

positisop

no profile record

コメント

positisop
·7 か月前·議論
github.com/NVIDIA/aistore

At the 1 billion valuation from the previous round, achieving a successful exit requires a company with deep pockets. Right now, Nvidia is probably a suitable buyer for MinIO, which might explain all the recent movements from them. Dell, Broadcom, NetApp, etc, are not going to buy them.
positisop
·7 か月前·議論
Raising 100 mil at 1 B valuation and then trying for an exit is a bitch!
positisop
·7 か月前·議論
If it is not an Apache/CNCF/LinuxFoundation project, it can be a rug pull aimed at using open source for getting people in the door only. They were never open for commits, and now they have abandoned open source altogether.
positisop
·7 か月前·議論
Raising 100 mil at 1 B valuation and then trying for an exit is a bitch!
positisop
·10 か月前·議論
Longhorn is a poorly implemented distributed storage layer. You are better off with Ceph.
positisop
·11 か月前·議論
NFS is its own spec, that is somewhat compliant with POSIX, and arguably FUSE is POSIX and can be used to implement a POSIX-compliant filesystem.
positisop
·11 か月前·議論
Please do not make decisions based on this article. It is a poorly written blog with typos and a lack of technical depth. The blog puts Goofys in the same bucket as JuiceFS and Alluxio.. A local NVMe populated via a high-throughput Object Store will give you the best performance. This blog does not go into the system architecture involved that prohibits static models from being pre-populated or the variations in the "FUSE" choices. I can see why AI startups need large amounts of money when the depth of engineering is this shallow.
positisop
·11 か月前·議論
Glad you wrote it, the title took me down the same path for a few seconds :-D
positisop
·11 か月前·議論
I think CS grads often skip the part of how something actually works and are happy with abstractions.
positisop
·昨年·議論
Google Cloud Storage had it for eons before S3. GCS comes across as a much better thought-out and built product.
positisop
·昨年·議論
They are not efficient; they have a one-time static hash to create a cluster. After that, it is all duct tape and glue. Want to expand? Add another cluster (pool) and then look for the cluster that contains the object. They don't know which cluster has the object, and performance does not scale as well with additional clusters. Want to decommission a single node, drain the cluster. They refer to multiple pools as a single cluster, but it is essentially a set of static hashes that lack the intelligence to locate objects. Got the initial EC configuration not quite right.. sorry need to redo the entire cluster.

MinIO is a good fit if you want a small cluster that doesn't require day 2 operational complexity, as you only store a few TBs.

I have not looked into them recently, but I doubt the core has changed. Being VC-funded and looking for an exit makes them overinvest in marketing and story telling.
positisop
·昨年·議論
Look under the hood, the limitations are based on the core, sticking a UI on it does not hide what needs to happen at scale.
positisop
·昨年·議論
Try expanding a cluster, or changing erasure coding configuration, or using anything that needs random access within a file (parquet), or any day 2 operation.