Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t14lG-00Ebyx-FR for pgsql-novice@arkaria.postgresql.org; Wed, 16 Oct 2024 14:12:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t14lE-003y3N-9v for pgsql-novice@arkaria.postgresql.org; Wed, 16 Oct 2024 14:12:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t14fj-003tXw-K2 for pgsql-novice@lists.postgresql.org; Wed, 16 Oct 2024 14:06:44 +0000 Received: from mail-lf1-x12a.google.com ([2a00:1450:4864:20::12a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t14fg-001Brr-PK for pgsql-novice@lists.postgresql.org; Wed, 16 Oct 2024 14:06:42 +0000 Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-539ebb5a20aso4345864e87.2 for ; Wed, 16 Oct 2024 07:06:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=keksi-io.20230601.gappssmtp.com; s=20230601; t=1729087598; x=1729692398; darn=lists.postgresql.org; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:sender:from:to:cc:subject:date:message-id:reply-to; bh=/A6NX/HcvX0l8y/tBOo/XobjKG0VvbCcDfHYngEKkmk=; b=x5WjRTxcqvF7NZ+AeqVK0pfH0Dnbx9z3Fv3xtgEkxyLZ3MDCSk6woI/f9tEPhQAMc+ YEWMieHTYyOYbJhKNB7tCQOGFG9gkYcBsC/xbefScwuuxzD5Qxvf1kJLUNTWluberSx0 bMdv+8zKRzy61ZpS4QSBgXfVZfpRL7VUl5v6o3knnkub9bcuG151ILiCQSB88573AWNq z546SU91a9lUwiRxAir43KppXgU6g5EXcWEVBdTc9YKh8/hkbZh0nO49j9H6rPh/DVvq Q0BmqlFJoTK1/KLHMwn4Q+lc6DOpv4KiiU9QjE9Fg6Xw6ilGWD2TGljbUCGUh0TvjFqx DmjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729087598; x=1729692398; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/A6NX/HcvX0l8y/tBOo/XobjKG0VvbCcDfHYngEKkmk=; b=QWEs6lB7xFjuMtFbaJkDx4LJ6BK9hYzsxgOvr7JZ1K0TgNP/DFDAJiX7cHlOlFkLBp xHoPhKxsCffb6yXm23MJF4Kla5FzWHwgYzdkxJ3raVVHUntZpzDhoS8OSUpmWFdhxb93 ga43MSwRLxMZuPGabzFDYMUt/1XZmqjsmM+IROTwFeVxoO3vFftPIJtfwphnnbUElbG3 NMQLzFwQYfMKVkPbwk2lJkpwt3WYmA8Fbii1TJ5DHWK9Q5JdInsK+to1W/HGsMYxEFe0 Hm02OBS1JrOb3+eqwqiwSY1by8JXQijmujYDph0ZhQ81DvvGGs45BzkRoafHyOfiwYyD xfBw== X-Gm-Message-State: AOJu0YyVJR1DQH7ydlE42e2STYvuQfqV8BmZJmUP025KOal0jdKCmkpD WZTC6UQ4pE6xr78iJI39Na6p1/oX4zbf/b4fLCYGnH1lM0etLnvXle/6iMBxOCZrq243PJ9GehN y X-Google-Smtp-Source: AGHT+IH6W6mQSMsgtgzs4xlK/yhCgKSmRU6DR8ASHS5tMLNpPHsAlZTbrIjLrOFMBGj5m1a/GMNy4A== X-Received: by 2002:a05:6512:3402:b0:539:959e:f0e8 with SMTP id 2adb3069b0e04-539e54f86c3mr7737905e87.21.1729087598126; Wed, 16 Oct 2024 07:06:38 -0700 (PDT) Received: from smtpclient.apple (87-95-72-136.bb.dnainternet.fi. [87.95.72.136]) by smtp.gmail.com with ESMTPSA id 2adb3069b0e04-539ffd54c2fsm467864e87.0.2024.10.16.07.06.36 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Oct 2024 07:06:36 -0700 (PDT) Sender: Onni Hakala From: Onni Hakala X-Google-Original-From: Onni Hakala Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\)) Subject: Recommendations on how to combine SSD and HDD drives in bare metal PostgreSQL server Message-Id: <89E7D559-F734-4739-9730-7EDDF787910D@flaky.build> Date: Wed, 16 Oct 2024 17:06:24 +0300 To: pgsql-novice@lists.postgresql.org X-Mailer: Apple Mail (2.3818.100.11.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hey, I have a large dataset of > 100TB which would be very expensive to store = solely into SSD drives. I have access to a server which has 2x 3.84TB NVME SSD disks and large = array of HDD drives 8 x 22TB. Most of the data that I have in my dataset is very rarely accessed and = is stored only for archival purposes. What would be the de-facto way to use both SSD and HDD together in a way = use where commonly used data would be fast to access and old data would = eventually only be stored in compressed format in the HDDs? I was initially looking into building zpool using zfs with raidz3 and = zstd compression for my HDDs but I=E2=80=99m unsure how to add the SSDs = into this equation and I thought that this is probably a common scenario = and wanted to ask opinions from here. Thanks in advance, Onni Hakala