all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: lord_Niedzwiedz <sir_Misiek1@o2.pl>
To: pve-user@pve.proxmox.com
Cc: "kkolator@poczta.onet.pl" <kkolator@poczta.onet.pl>
Subject: [PVE-User] CEPH - benchmark
Date: Tue, 19 Sep 2023 12:28:33 +0200	[thread overview]
Message-ID: <0f30b423-7ba9-8cdc-11c1-23929f8ff37d@o2.pl> (raw)

         I have non heterogenic network and hardware.
CEPH about        Write 1160MB/sec,     Read 1820 MB/sec

One nvme drive started going crazy.
The performance of the entire array dropped catastrophically.
The system said nothing.
I wonder if there is any mechanism in CEPH/Proxmox that informs us about 
this automatically ??


I quickly wrote a script that periodically checks performance.

root@tjall1:~# cat /Backup/script/Ceph.sh

#!/bin/sh
#        Ceph test by sir_Misiek@o2.pl
#        Grzegorz Mi$kiewicz
#        19.09.2023

MINWRITE=600
MINREAD=1200
POOL1=ceph-lxc
POOL2=ceph-vm

WRITE=`rados bench -p $POOL1 120 write --no-cleanup | grep "Bandwidth "| 
awk '{ print $3}'`
READ=`rados bench -p $POOL1 60 rand| grep "Bandwidth "| awk '{ print $3}'`

  echo Write = $WRITE
  echo READ = $READ

# We cut out everything before the dot. Converts a floating point value 
to an integer.
WRITE_INT=${WRITE%%.*}
READ_INT=${READ%%.*}

if [ ${MINWRITE} -ge "${WRITE_INT}" ]; then
     echo "Ceph slow write on pool($POOL1): ${WRITE} MB/sec"
   fi

if [ ${MINREAD} -ge "${READ_INT}" ]; then
     echo "Ceph slow read on pool($POOL1): ${WRITE} MB/sec"
   fi

rados -p $POOL1 cleanup > /dev/null
rados -p $POOL1 cleanup; sync; rados -p $POOL2 cleanup; sync

exit




                 reply	other threads:[~2023-09-19 10:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0f30b423-7ba9-8cdc-11c1-23929f8ff37d@o2.pl \
    --to=sir_misiek1@o2.pl \
    --cc=kkolator@poczta.onet.pl \
    --cc=pve-user@pve.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal