This directory contains the source code for the Skytable Shell. When compiled, it produces a single binary `skysh`, short for **Sky**table **s**hell. The Skytable shell can be used to connect to a Skytable instance and it provides some nice to have shell features like history, terminal interactions and more.
By default, `skysh` connects to the `default:default` entity for an instance running on `127.0.0.1` (localhost) on port `2003`. You can change these connection settings use command-line parameters.
## License
All files in this directory are distributed under the [AGPL-3.0 License](../LICENSE).
Harness is the custom build tool that is used by Skytable as a "test harness" while also providing bundling/packaging functions. The `Makefile` at the root of the source tree builds the `harness` binary and then runs respective commands using the harness binary (such as `test`, `build`, ...).
## License
All files in this directory are distributed under the [AGPL-3.0 License](../LICENSE).
This directory contains the source code for the Skytable database server (the "actual database"). When compiled, it produces a single binary `skyd`, short for **Sky**table **d**aemon. The daemon serves the clients over a network.
## License
All files in this directory are distributed under the [AGPL-3.0 License](../LICENSE).
`sky-bench` is Skytable's benchmarking tool. Unlike most other benchmarking tools, Skytable's benchmark
tool doesn't do anything "fancy" to make benchmarks appear better than they are. As it happens, the benchmark tool might show Skytable to be slower!
Here's how the benchmark tool works (it's dead simple):
1. Depending on the configuration it launches "network pools" which are just thread pools where each worker
holds a persistent connection to the database (something like a connection pool)
2. A collection of unique, random keys are generated using a PRNG provided by the `rand` library that is
seeded using the OS' source of randomness. The values are allowed to repeat
3. The [Skytable Rust driver](https://github.com/skytable/client-rust) is used to generate _raw query packets_. To put it simply, the keys and values are turned into `Query` objects and then into the raw bytes that will be sent over the network. (This just makes it simpler to design the network pool interface)
4. For every type of benchmark (GET,SET,...) we use the network pool to send all the bytes and wait until we receive the expected response. We time how long it takes to send and receive the response for all the queries for the given test (aggregate)
5. We repeat this for all the remaining tests
6. We repeat the entire set of tests 5 times (by default, this can be changed).
7. We do the calculations and output the results.
## License
All files in this directory are distributed under the [AGPL-3.0 License](../LICENSE).
The Skytable migration tool can be used to perform migrations between database versions. The basic idea is:
"read all data from the older machine and send it over to the newer one."
For migrating versions from 0.6 to 0.7, the database administrator has to launch the tool in the old data directory of the old instance and then pass the new instance host/port information. The tool will then read the data from the directory (this was possible because 0.6 used a very simple disk format than newer versions). This approach however has the advantage of not having to start the database server for the migration to happen.
## License
All files in this directory are distributed under the [AGPL-3.0 License](../LICENSE).
This is a tool in its infancy, but its ultimate goal is to provide a stress testing framework for Skytable. For now, it tests linearity (core scalability) with increasing clients.
## License
All files in this directory are distributed under the [AGPL-3.0 License](../LICENSE).
Sayan Nandan
2 years ago