Live data from Hacker News

Wasabi – Simple storage solution

wasabi.com

101–110 of 164 posts

Re: Wasabi – Simple storage solution

#101
post #95

Earlier quoted context omitted.

B2 is horribly unstable, has limits left and right and most of all, the latency is horrendous. You will be better off using any standard OpenStack provider. That way you won't have a lock in, and great performance (in my testing). E.g. OpenStack Swift on OVH. Sure it's a tiny bit more expensive. But you get a mature cross-provider API and better performance. Even for huge chunks of cold data, I wouldn't want to use B…

What are some good OpenStack providers? and are there any that can 11 nines durability?

[deleted]

Re: Wasabi – Simple storage solution

#102
post #73
post #70

Wouldn't it be funny if this was just a market test/exercise, using actual S3 as a backend, just to see if it gets any traction before building own HW/SW solution?

Kind of like how most wasabi in the U.S. isn't really wasabi, it's just horseradish? lol

Well if this service were called horseradish I would definitely sign up.

Re: Wasabi – Simple storage solution

#103
post #97

Some quick observations: - Their performance claims are incredibly biased. Amazon S3 has far better write performance than their claims. - They claim 100% S3 compatibility but it fails a large number of API calls using Ceph’s s3-test. I didn’t dig into this too far but they do claim “No need to change your S3-compatible application” so changing my endpoint + credentials should have worked. To their credit - PUT, GET…

>Their first round was debt financing. Are you suggesting that Wasabi might go away because, maybe, this is not the "traditional" valley model?

Many, many startups in the valley have raised on convertible notes (aka debt) first.

Re: Wasabi – Simple storage solution

#105

On the same page on HN there's another Wasabi that's a fire alarm for deaf people.

And I'm old enough to remember Wasabi as the proprietary vb-to-php compiler that FogCreek developed for a few years. And I think there was something related to OpenBSD or NetBSD, some company called Wasabi System...?

It's definitely one of the most common codenames in IT, together with Phoenix, Firebird and Panda (and in the enterprise, all greek/roman gods).

Re: Wasabi – Simple storage solution

#106
post #70

Wouldn't it be funny if this was just a market test/exercise, using actual S3 as a backend, just to see if it gets any traction before building own HW/SW solution?

Their IP addresses belong to a company named PSI net:

    ~ dig +short console.wasabisys.com
  38.27.106.13
  38.27.106.12
  38.27.106.11

  NetRange:       38.0.0.0 - 38.255.255.255
  CIDR:           38.0.0.0/8
  NetName:        COGENT-A
  NetHandle:      NET-38-0-0-0-1
  Parent:          ()
  NetType:        Direct Allocation
  OriginAS:       AS174
  Organization:   PSINet, Inc. (PSI)
  RegDate:        1991-04-16
  Updated:        2011-05-20
  Comment:        Reassignment information for this block can be found at
  Comment:        rwhois.cogentco.com 4321
  Ref:            https://whois.arin.net/rest/net/NET-38-0-0-0-1
There's not much to be found by PSINet or Cogent who own them, but they don't seem to offer hosting services. The only relevant piece of information that I could find as to what PSINet do these days is this one:

https://forums.digitalpoint.com/threads/lots-of-weird-traffi...

It does make it sound as if it is a market test, or that PSINet have developed large scale hosting capabilities in the last few years.

// Edit

In addition, they use the exact same terminology Amazon uses in their console file, including ARN and two policies named after S3:

AmazonS3FullAccess AmazonS3ReadOnlyAccess

The policy syntax looks familiar to those coming from S3 as well.

Re: Wasabi – Simple storage solution

#107
post #94

Earlier quoted context omitted.

The benefit of S3 is that traffic is free within the same region. If you're hosting on AWS that alone is going to save you money versus the competitors.

A less seen cost is for the various operations. Regularly pushing lots of small files on S3 can get expensive. $1/200k files ($0.005 per 1k PUT requests).

Not to mention the minimum file size charge, which I think was a few kb per file in infrequent access S3.

Re: Wasabi – Simple storage solution

#108
post #106
post #70

Wouldn't it be funny if this was just a market test/exercise, using actual S3 as a backend, just to see if it gets any traction before building own HW/SW solution?

Their IP addresses belong to a company named PSI net: ~ dig +short console.wasabisys.com 38.27.106.13 38.27.106.12 38.27.106.11 NetRange: 38.0.0.0 - 38.255.255.255 CIDR: 38.0.0.0/8 NetName: COGENT-A NetHandle: NET-38-0-0-0-1 Parent: () NetType: Direct Allocation OriginAS: AS174 Organization: PSINet, Inc. (PSI) RegDate: 1991-04-16 Updated: 2011-05-20 Comment: Reassignment information for this block can be found at Com…

Cogent bought PSINET some time ago. http://www.cogentco.com/en/news/press-releases/279-cogent-co...

Cogent has large scale hosting capability

Re: Wasabi – Simple storage solution

#109

Lacking comparison with their closest competitor B2 ($0.005/GB, cheaper outbound at $0.02/GB). Also no information on DC location and zones.

They claim to have multiple data centers. It sounds fishy to me. I would like to see some pics / info af their setup before I trust them with 1 byte of my data.

Re: Wasabi – Simple storage solution

#110
post #105

On the same page on HN there's another Wasabi that's a fire alarm for deaf people.

And I'm old enough to remember Wasabi as the proprietary vb-to-php compiler that FogCreek developed for a few years. And I think there was something related to OpenBSD or NetBSD, some company called Wasabi System...? It's definitely one of the most common codenames in IT, together with Phoenix, Firebird and Panda (and in the enterprise, all greek/roman gods).

NetBSD, and also storage related[0], confusingly enough. Wasabi brought journaling (WAPBL[1]) to NetBSD.

[0] http://www.wasabisystems.com/

[1] http://netbsd.gw.com/cgi-bin/man-cgi?wapbl++NetBSD-current

Post reply on HN