Be Right Back

[Scott Greczkowski]

We will be offline for a few second as we reboot to load a new server kernel. We won't be down long.

 

[Scott Greczkowski]

Forgot to post we are back up. Lol.

 

[TheKrell]

Forgot to post we are back up. Lol.

Well, if you weren't, how would we know?

 

[Howard Simmons]

Forgot to post we are back up. Lol.

 

[TheForce]

Saturday Morning- The site is very slow. Took 30 seconds to just bring up this thread.

 

[TRG]

Same here.

 

[Scott Greczkowski]

I started a database dump this morning and it look like it slowed everything down. Was just trying to back thing up to a second server.

 

[TheForce]

Much better now.

 

[TheKrell]

I started a database dump this morning and it look like it slowed everything down. Was just trying to back thing up to a second server.

I don't remember backups slowing things to a crawl before, as this one did! What's different? Is the second server on-site? If so, it might have flooded the network interface. Just speculating...

 

[Scott Greczkowski]

It did the dump but had issues compressing the database and that's where I found it using all the CPU. Killed Gzip and speed came back.

This happened once before on the old server.

I would have noticed sooner if I didn't fall back asleep. I was laying in bed and one of the dogs came and laid on me and I feel back to sleep and woke up two hours later. Lol.


Sent from my iPhone using Tapatalk

 

[TheKrell]

Killed Gzip and speed came back.

gzip is single-threaded and you presumably had only one instance running so... How did that max out your powerful new server with (how many?) multiple cores.

I moved to pigz because of that, because my server was only making compressed tarballs and I had a plenty of cores to consume.