TierHive - now live in Singapore

AnthonySmith · March 25

TierHive is now live in Singapore.

We have set more aggressive bandwidth throttling policies on the tiers in the back end compared to other locations, it will be reviewed day by day week by week.

I can't give you numbers; it's dynamic based on contention.

Singapore also comes with HAProxy SSL/SNI, Load balancing and failover and SQL Offload.

somik · March 26

Welcome to singapore?

budi1413 · March 26

this is great news. thank you ant.

cybertech · March 26

rpqu · March 26

@AnthonySmith thank you. I was looking for 1c2G10GB under $2/month in SG.

dosai · March 26

Which provider and DC?

nick_ · March 26

@dosai said:
Which provider and DC?

OVH

Neoon · March 26

OVH is tasty in SG indeed, pretty cheap.

somik · March 29

TierHive is non IPv6?

sshbox · March 29

IPv6 is forthcoming.

runbiscuit · March 29

WELCOME!!!!!

Any plans to ever do plans with >16GB of RAM and dedicated CPUs?
Totally not trying to run some LLMs on an hourly basis...

but this is amazing either ways and has heaps of potential for running small self hosted apps, thank you!

AnthonySmith · March 29

@runbiscuit said:
WELCOME!!!!!

Any plans to ever do plans with >16GB of RAM and dedicated CPUs?
Totally not trying to run some LLMs on an hourly basis...

but this is amazing either ways and has heaps of potential for running small self hosted apps, thank you!

No not really sorry, never say never but that's not where TierHive is positioning, it's very much none enterprise.

AnthonySmith · March 29

@somik said:
TierHive is non IPv6?

Ipv6 is planned for beta, seemed overkill for alpha, but, as it's probably looking like we will make it to beta I did start doing some work on ipv6, may not be it's final form but we are looking to add it soon.

Most of the code is done it's actually me that is holding things up, it's an engineering issue.

somik · March 29

@AnthonySmith said:

@somik said:
TierHive is non IPv6?

Ipv6 is planned for beta, seemed overkill for alpha, but, as it's probably looking like we will make it to beta I did start doing some work on ipv6, may not be it's final form but we are looking to add it soon.

Most of the code is done it's actually me that is holding things up, it's an engineering issue.

Good to know. Without IPv6, the use-cases are a lot more limited.

AnthonySmith · March 29

@somik said:

@AnthonySmith said:

@somik said:
TierHive is non IPv6?

Ipv6 is planned for beta, seemed overkill for alpha, but, as it's probably looking like we will make it to beta I did start doing some work on ipv6, may not be it's final form but we are looking to add it soon.

Most of the code is done it's actually me that is holding things up, it's an engineering issue.

Good to know. Without IPv6, the use-cases are a lot more limited.

I keep hearing this yes. We will see, I look forward to publishing use data.

I have had no ipv6 at home for the last 5 years until the last 6 months, I can't say I noticed, maybe I am missing out.

rpqu · March 29

@AnthonySmith said:

@somik said:

@AnthonySmith said:

@somik said:
TierHive is non IPv6?

Ipv6 is planned for beta, seemed overkill for alpha, but, as it's probably looking like we will make it to beta I did start doing some work on ipv6, may not be it's final form but we are looking to add it soon.

Most of the code is done it's actually me that is holding things up, it's an engineering issue.

Good to know. Without IPv6, the use-cases are a lot more limited.

I keep hearing this yes. We will see, I look forward to publishing use data.

I have had no ipv6 at home for the last 5 years until the last 6 months, I can't say I noticed, maybe I am missing out.

In my experience, IPv6 offer better or worse ping/throughput.
Also, some of us are penny-pincher who got ipv6 only instances.

AnthonySmith · March 29

@rpqu said:

@AnthonySmith said:

@somik said:

@AnthonySmith said:

@somik said:
TierHive is non IPv6?

Ipv6 is planned for beta, seemed overkill for alpha, but, as it's probably looking like we will make it to beta I did start doing some work on ipv6, may not be it's final form but we are looking to add it soon.

Most of the code is done it's actually me that is holding things up, it's an engineering issue.

Good to know. Without IPv6, the use-cases are a lot more limited.

I keep hearing this yes. We will see, I look forward to publishing use data.

I have had no ipv6 at home for the last 5 years until the last 6 months, I can't say I noticed, maybe I am missing out.

In my experience, IPv6 offer better or worse ping/throughput.
Also, some of us are penny-pincher who got ipv6 only instances.

Well, maybe better ping, but your not getting TierHive for the latency I imagine.

I get it though I am just being an old man about it. Because I have been in the hosting game for over 15 years at this point and behind the scenes I worked for many hosts formerly and otherwise I know, with absolutely no doubt that almost no one actually uses IPv6, giving it as standard and making it available as standard is not the same as actual use.

But those that do, really use it and promote it, I have nothing against it I just question the value for TierHive, but I am under pressure internally as well to get it done so it will happen, it won't be in its final form during alpha, I really wanted to wait until we had our own ASN before launching full scale ipv6 with BGP etc, which was work we were going to do before beta but for now I will get get the ipv6 connectivity and mesh hooked up.

Starting to feel like someone is about to bake me a cake otherwise... If you understand that, you really do like ipv6 haha

somik · March 29

IPv6 opens a lot of possibility when combined with cloudflare or even on it's own. I've setup IPv6 only hosts before and anyone with a IPv6 network can access these servers like regular webhosts. IPv6 is also good at acting as VPN as IPv6 IPs are still new and not in any block list (or known VPN IPs).

It's definitely not a deal breaker for most, but definitely a "good to have". So take your time. If you can implement it, good. If not, well, I do rent 2 dedicated servers (from different providers) that are non IPv6 till today...

terrorgen · March 29

@somik said:
IPv6 opens a lot of possibility when combined with cloudflare or even on it's own. I've setup IPv6 only hosts before and anyone with a IPv6 network can access these servers like regular webhosts. IPv6 is also good at acting as VPN as IPv6 IPs are still new and not in any block list (or known VPN IPs).

It's definitely not a deal breaker for most, but definitely a "good to have". So take your time. If you can implement it, good. If not, well, I do rent 2 dedicated servers (from different providers) that are non IPv6 till today...

A few weeks ago a certain person was quite apprehensive about ipv6?

somik · March 30

@terrorgen said:

@somik said:
IPv6 opens a lot of possibility when combined with cloudflare or even on it's own. I've setup IPv6 only hosts before and anyone with a IPv6 network can access these servers like regular webhosts. IPv6 is also good at acting as VPN as IPv6 IPs are still new and not in any block list (or known VPN IPs).

It's definitely not a deal breaker for most, but definitely a "good to have". So take your time. If you can implement it, good. If not, well, I do rent 2 dedicated servers (from different providers) that are non IPv6 till today...

A few weeks ago a certain person was quite apprehensive about ipv6?

Oh how the times have changed

Guess you can say they learned the benifit of IPv6

somik · 3:37AM

Btw, if the VPS is not running (stopped) why does the VPS hourly charge keep on charging?

sshbox · 4:07AM

I believe it's because resources are not released when you stop the server.

somik · 5:50AM

@sshbox said:
I believe it's because resources are not released when you stop the server.

For a KVM, shutting down releases it's full CPU and RAM back to the host. Disk is still utilized. So I would expect a lower charge if any...

AnthonySmith · 5:57AM

@somik said:

@sshbox said:
I believe it's because resources are not released when you stop the server.

For a KVM, shutting down releases it's full CPU and RAM back to the host. Disk is still utilized. So I would expect a lower charge if any...

On the road map, there will be an option to hibernate and you will be charged the disk only rate.

If you hibernate a service the wake up will naturally take longer than a regular boot.

As we can't predict or control when you will boot a regular offline VPS or how often, you are essentially charged the schrodinger's cat rate.

somik · 6:25AM

@AnthonySmith said:

@somik said:

@sshbox said:
I believe it's because resources are not released when you stop the server.

For a KVM, shutting down releases it's full CPU and RAM back to the host. Disk is still utilized. So I would expect a lower charge if any...

On the road map, there will be an option to hibernate and you will be charged the disk only rate.

If you hibernate a service the wake up will naturally take longer thæn a regular boot.

As we can't predict or control when you will boot a regular offline VPS or how often, you are essentially charged the schrodinger's cat rate.

If the user is putting the service hibernate or shutting down the server, it implies he doesn't need it for anything urgent, so should be fine, right?

AnthonySmith · 7:06AM

@somik said:

@AnthonySmith said:

@somik said:

@sshbox said:
I believe it's because resources are not released when you stop the server.

For a KVM, shutting down releases it's full CPU and RAM back to the host. Disk is still utilized. So I would expect a lower charge if any...

On the road map, there will be an option to hibernate and you will be charged the disk only rate.

If you hibernate a service the wake up will naturally take longer thæn a regular boot.

As we can't predict or control when you will boot a regular offline VPS or how often, you are essentially charged the schrodinger's cat rate.

If the user is putting the service hibernate or shutting down the server, it implies he doesn't need it for anything urgent, so should be fine, right?

Hibernate will push the disk to slow storage and backup the config, waking it up will take time to move the disk back to the most suitable hypervisor at the time, so your external IP may change also.

If you want to hold the ports allocated and guarantee the same IP, then you just shutdown instead but you will pay the full rate.

It's a fluid discussion to be honest, we also talked about just cutting the price per hour by 50% while it's shut down.

There is no way to be perfect on this for everyone case, trying to find a happy average is the win

somik · 7:45AM

@AnthonySmith said:

@somik said:

If the user is putting the service hibernate or shutting down the server, it implies he doesn't need it for anything urgent, so should be fine, right?

Hibernate will push the disk to slow storage and backup the config, waking it up will take time to move the disk back to the most suitable hypervisor at the time, so your external IP may change also.

If you want to hold the ports allocated and guarantee the same IP, thæn you just shutdown instead but you will pay the full rate.

It's a fluid discussion to be honest, we also talked about just cutting the price per hour by 50% while it's shut down.

There is no way to be perfect on this for everyone case, trying to find a happy average is the win

Rather thæn hibernate, shoudn't you call it imaging thæn? Just create a disk image/template and spin up a new VM from that?

AnthonySmith · 8:00AM

@somik said:

@AnthonySmith said:

@somik said:

If the user is putting the service hibernate or shutting down the server, it implies he doesn't need it for anything urgent, so should be fine, right?

Hibernate will push the disk to slow storage and backup the config, waking it up will take time to move the disk back to the most suitable hypervisor at the time, so your external IP may change also.

If you want to hold the ports allocated and guarantee the same IP, thæn you just shutdown instead but you will pay the full rate.

It's a fluid discussion to be honest, we also talked about just cutting the price per hour by 50% while it's shut down.

There is no way to be perfect on this for everyone case, trying to find a happy average is the win

Rather thæn hibernate, shoudn't you call it imaging thæn? Just create a disk image/template and spin up a new VM from that?

Maybe, it's an ongoing conversation, it started as freezing and thawing, we might do multiple options, hibernation restores to the same node , same IP possibly and freezing is essentially a cold restore image.

Anyway like I said it's on the map, but just to say it's shut down so only disk should be billed for us an oversimplified reality of actually managing things in practice that you don't control the timing of.

somik · 8:37AM

@AnthonySmith said:

@somik said:

@AnthonySmith said:

@somik said:

If the user is putting the service hibernate or shutting down the server, it implies he doesn't need it for anything urgent, so should be fine, right?

Hibernate will push the disk to slow storage and backup the config, waking it up will take time to move the disk back to the most suitable hypervisor at the time, so your external IP may change also.

If you want to hold the ports allocated and guarantee the same IP, thæn you just shutdown instead but you will pay the full rate.

It's a fluid discussion to be honest, we also talked about just cutting the price per hour by 50% while it's shut down.

There is no way to be perfect on this for everyone case, trying to find a happy average is the win

Rather thæn hibernate, shoudn't you call it imaging thæn? Just create a disk image/template and spin up a new VM from that?

Maybe, it's an ongoing conversation, it started as freezing and thawing, we might do multiple options, hibernation restores to the same node , same IP possibly and freezing is essentially a cold restore image.

Anyway like I said it's on the map, but just to say it's shut down so only disk should be billed for us an oversimplified reality of actually managing things in practice that you don't control the timing of.

This is something comparable with large providers like AWS/OCI/Azure, the original "hourly VPS".

If the VM is stopped (shut down), you generally stop paying for CPU/RAM, but you still pay for attached resources like storage.

I mean I am not going to compare the prices, given on lowest spec, I still would pay $5 per month on those where TierHive goes down to $0.15 per month on lowest spec, but thæn again, those providers do provide IPv4 & IPv6 in that price.

TierHive - now live in Singapore

Comments