# Last week in scylladb.git master (issue #230; 2024-05-19)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-230-2024-05-19/2041>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [May 19, 2024, 3:20pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-230-2024-05-19/2041 "2024-05-19T15:20:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![avikivity](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/avikivity/32/38_2.png) [@avikivity](https://forum.scylladb.com/u/avikivity)\
**Post date:** [May 19, 2024, 3:20pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-230-2024-05-19/2041/1 "2024-05-19T15:20:17Z")

</div>

This short report brings to light some interesting commits to [scylladb.git master](https://github.com/scylladb/scylladb/) from the last week. Commits in the 2ad13e5d76…c93a7d2664 range are covered.

There were 96 non-merge commits from 23 authors in that period. Some notable commits:

  

Alternator, ScyllaDB’s implementation of the DynamoDB API, now includes an [end-to-end benchmark](https://github.com/scylladb/scylladb/commit/9813ec944641f107029c040f7d8b5c1958230258) (including the HTTP server).

With tablets, each tablet replica’s sstables are isolated in a storage group. We now [dynamically allocate](https://github.com/scylladb/scylladb/commit/c8cc47df2debf83acd45d571a41c38897d968d6a) these storage groups only when a node actually hosts a particular tablet. This saves memory and allows for large tables.

The container image [no longer contains](https://github.com/scylladb/scylladb/commit/3eb81915c1c09e3d26c75580a0b45251c28feda5) the JMX server and cassandra-stress.

The bundled cqlsh version was [updated](https://github.com/scylladb/scylladb/commit/a1a6bd67987b5703962d3655eeb5004f92bf42f3) to v6.0.18.

The iotune utility is used to measure a disk’s performance when installing ScyllaDB. It now works when executed on machines with a [very large core count](https://github.com/scylladb/scylladb/commit/ec820e214ca87cc741d1edd4a70d677ea8497e07).

A performance problem with range scans on tablets was [fixed](https://github.com/scylladb/scylladb/commit/0b2ec3063cb7c08a17fced26ae27f11e7ebda5be).

There are now some [metrics reported per table](https://github.com/scylladb/scylladb/commit/0c84692c971a2c6245118c77a060d303b171f5d2). The metrics are not reported per shard to avoid a combinatorial explosion.

The DESCRIBE TABLES command now [omits](https://github.com/scylladb/scylladb/commit/9ab57b12bb03bdd219f0235f5b77cd1b72a39d95) the special CDC tables. These aren’t needed to restore the schema since the base CREATE TABLE command will recreate them.

ScyllaDB disseminates the materialized view update backlog in order to control update rates. A bug that prevented this in some circumstances was [fixed](https://github.com/scylladb/scylladb/commit/5154429713134e9b01567a48acbd186e8c7f0052).

The [nodetool ring](https://github.com/scylladb/scylladb/commit/a5fea84d827fcb1e2e81d6476a61d9f1c5e1df27) command now supports tablets.

Materialized views now [throttle updates better](https://github.com/scylladb/scylladb/commit/68eca3778c2f4f58118863a9671750cc559a3573), when an update generates a large amount of materialized view writes.

A hang on some CQL queries with redundant constraints was [fixed](https://github.com/scylladb/scylladb/commit/27ab560abd30a5fc43174c45d2f8ae2116987b13).

  

See you in the next issue of last week in scylladb.git master!