91–100 of 329 posts
> Currently, only the us-east-1 region is supported. Please contact support@regattastorage.com if you need to use a different region. Bold choice, given what I know about us-east-1
Total curiosity, but what’s the limiting factor of scaling out to multiple regions day one.
Interesting. Reminds me of FlexFS ( https://flexfs.io/ ). I spoke to a very knowledgeable person there when investigating what to use but we ended up using EFS instead. An annoying feature of EFS is how it scales with amount of storage, so when its empty its very slow. We also started hitting its limits so could not scale our compute workers. Both can be solved by paying for the elastic iops but that is VERY expensiv…
Out of curiosity, why did you choose EFS, it's insanely expensive at even modest scales?
How does this differ from AWS Storage Gateway?
Great question! We fill the same role as AWS Storage Gateway (and I used to work closely with that team when I was at AWS, lots of respect for what they do). AWS Storage Gateway is built primarily as an appliance to be installed on instances in your own data center to ease migration to the cloud. Many customers do deploy Storage Gateway on EC2 because they want these features in the cloud itself. However, the "appliance" design of Storage Gateway makes it unsuitable for this purpose. For example, Storage Gateway is not designed to run in a cluster for high-availability and doesn't have access to durable, long-term storage to stage and cache writes.
On the other hand, Regatta is designed as a cloud-native gateway product. Regatta's elastic, durable caching layer allows us to efficiently cache large data sets without thrashing, and always efficiently perform writes. Because Regatta is designed to be highly-available, customers don't have to worry about downtime for patching or deployments.
* What does "$0.05 / gigabyte transferred" mean exactly. Transferred outside of AWS or accessed as in read and written data?
* "$0.20/GiB-mo of high-speed cache" – how is the high-speed cache amount computed?
Why are you guys hijacking the scroll bar on your website?
Pretty sure we're in your target market. We [0] currently use GCP Filestore to host DuckDB. Here's the pricing and performance at 10 TiB. Can you give me an idea on the pricing and performance for Regatta? Service Tier: Zonal Location: us-central1 10 TiB instance at $0.35/TiB/hr Monthly cost: $2,560.00 Performance Estimate: Read IOPS: 92,000 Write IOPS: 26,000 Read Throughput: 2,600 MiB/s Write Throughput: 880 MiB/s…
Yes, you should be in our target market. I don't think that I can give a cost estimate without having a good sense of what percentage of your data you're actively using at any given time, but we should absolutely support the performance numbers that you're talking about. I'd love to chat more in detail, feel free to send me a note at hleath [at] regattastorage.com.
Found this in the docs:
> By default, Regatta file systems can provide up to 10 Gbps of throughput and 10,000 IOPS across all connected clients.
Is that the lower bound? The 50 TiB filestore instance has 104 Gbps read through put (albeit at a relatively high price point).
How does this compare to Amazon's own offering in this space, the "AWS Storage Gateway"? It can also back various storage protocols with S3, using SSDs for cache, etc. ( https://aws.amazon.com/storagegateway/features/ )
Great question! We fill the same role as AWS Storage Gateway (and I used to work closely with that team when I was at AWS, lots of respect for what they do). AWS Storage Gateway is built primarily as an appliance to be installed on instances in your own data center to ease migration to the cloud. Many customers do deploy Storage Gateway on EC2 because they want these features in the cloud itself. However, the "applia…
Can you elaborate on a few things with regards to your pricing: * What does "$0.05 / gigabyte transferred" mean exactly. Transferred outside of AWS or accessed as in read and written data? * "$0.20/GiB-mo of high-speed cache" – how is the high-speed cache amount computed?
We need to update the home page with these details, but $0.05 is only charged on transfer between Regatta and S3. We calculate your cache usage minutely and tally it into a monthly usage amount that we then bill for.