CloudatCost Issues

02:40:09 PM CPU %user %nice %system %iowait %steal %idle
02:50:01 PM all 4.20 0.00 2.38 48.13 0.00 45.28

Yikes!

scottalanmiller

02:40:09 PM CPU %user %nice %system %iowait %steal %idle
02:50:01 PM all 4.20 0.00 2.38 48.13 0.00 45.28

Yikes!

Yikes indeed. Were you doing updates during that time? I'm hoping that's not the average when idle! I mean, that's scary when running updates for sure, still.

MangoLassi, running very hot today, hit only .16%, by comparison.

IRJ

When I first logged into my server it said rebuild failed. I hit retry and it only took 20 seconds to build successfully

IRJ

Boot up was really fast and I had a console connection completed in another 45 seconds or so.

@IRJ said:

When I first logged into my server it said rebuild failed. I hit retry and it only took 20 seconds to build successfully

Sound like a bad build, I had a couple. Can you access via SSH?

IRJ

No I cannot. I think it may be blocked on my network though. I will try when I get home

scottalanmiller

@IRJ said:

When I first logged into my server it said rebuild failed. I hit retry and it only took 20 seconds to build successfully

That's mostly what I've seen.

AmanBhogal

Hey guys!!
I just spoke with the team. We have some hardware upgrades happening this week that will likely increase any IO issues you may be having. in short, we have just ordered a ton of hardware to be able to provide better service and keep everybody happy

edit: I selected my words poorly. i said increase IO issues, when in reality I meant that it will help resolve issues

scottalanmiller

@AmanBhogal said:

Hey guys!!
I just spoke with the team. We have some hardware upgrades happening this week that will likely increase any IO issues you may be having. in short, we have just ordered a ton of hardware to be able to provide better service and keep everybody happy

Thanks. Keep us updating as the new hardware rolls out.

Danp

@AmanBhogal said:

will likely increase any IO issues you may be having.

I'm "left brained" so I always take things literally. Do you expect things to get better or worse in the short term?

scottalanmiller

@Danp said:

@AmanBhogal said:

will likely increase any IO issues you may be having.

I'm "left brained" so I always take things literally. Do you expect things to get better or worse in the short term?

I'm Aspy so I'm as literally as they get. I totally saw that typo too and was like.. hmmmm....

coliver

@Danp said:

@AmanBhogal said:

will likely increase any IO issues you may be having.

I'm "left brained" so I always take things literally. Do you expect things to get better or worse in the short term?

I was wondering the same thing. From the context I assume it means things are going to get better. But from how it is written it looks like things will get worse.

AmanBhogal

@coliver

doh!
Get Better!

AmanBhogal

@Danp
Better! that was me not choosing my words correctly

Something dark & ominous emerges from the jungle. Phew, it's just your ServerBear benchmark report!

View Your ServerBear Benchmark Online

UnixBench score: 746.4

I/O rate: 27.0 MB/second

Bandwidth rate: 5.9 MB/second

We hope you had a warm & fuzzy experience using ServerBear. Be sure to tell like minded mammals!

Grizzly Regards,

The ServerBear Team

This was a Developer 1 package, with nothing running but fully up to date.

scottalanmiller

It hit over 1300 IOPS.

scottalanmiller

I'm grabbing a report on a BigDog for you for comparison.

I haven't noticed any issues with my BigDog Instance. Likely there are simply less of those competting for resources.

scottalanmiller

@thecreativeone91 said:

I haven't noticed any issues with my BigDog Instance. Likely there are simply less of those competting for resources.

Presumably that means that there are dedicated servers for BigDogs and different ones for Dev1s. Completely possible, just saying.