te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>InfluxDB Measurements - One Bucket for All Customers or One per Customer? - Stack Overflow

你的位置：首页>programmer>InfluxDB Measurements - One Bucket for All Customers or One per Customer? - Stack Overflow

InfluxDB Measurements - One Bucket for All Customers or One per Customer? - Stack Overflow

programmeradmin2025-02-224浏览0评论

I’m currently using InfluxDB OSS 2 and plan to migrate to version 3 in the future.

My scenario:

I have around 100 customers, each with 100 measurements - Additionally, we expect to add up to 100 new customers annually.
Data is written to InfluxDB every 10 seconds.
Customers can retrieve only their own measurements via our REST API.

Currently, a retention policy of one month is sufficient for our needs. However, I'm unsure about the future needs of the customers. For example, if a customer wants to keep their data for a year or longer, the data retention requirements may change.

A single InfluxDB 2.7 OSS instance supports approximately 20 buckets actively being written to or queried across all anizations depending on the use case. Any more than that can adversely affect performance.

Create a bucket - Bucket limits

Now, I’m wondering: Should I use a single bucket for all customers or create a separate bucket for each customer?

与本文相关的文章