Compare commits
1 Commits
master
...
it-writing
| Author | SHA1 | Date | |
|---|---|---|---|
8cad2b0b5a
|
@@ -19,121 +19,7 @@
|
||||
<div class="slides">
|
||||
|
||||
<!-- Use external markdown resource, separate slides by three newlines; vertical slides by two newlines -->
|
||||
<section data-markdown="markdown.md" data-separator="^\n\n\n" data-separator-vertical="^\n\n"></section>
|
||||
|
||||
<!-- Slides are separated by three dashes (the default) -->
|
||||
<section data-markdown>
|
||||
<script type="text/template">
|
||||
## Demo 1
|
||||
Slide 1
|
||||
---
|
||||
## Demo 1
|
||||
Slide 2
|
||||
---
|
||||
## Demo 1
|
||||
Slide 3
|
||||
</script>
|
||||
</section>
|
||||
|
||||
<!-- Slides are separated by regexp matching newline + three dashes + newline, vertical slides identical but two dashes -->
|
||||
<section data-markdown data-separator="^\n---\n$" data-separator-vertical="^\n--\n$">
|
||||
<script type="text/template">
|
||||
## Demo 2
|
||||
Slide 1.1
|
||||
|
||||
--
|
||||
|
||||
## Demo 2
|
||||
Slide 1.2
|
||||
|
||||
---
|
||||
|
||||
## Demo 2
|
||||
Slide 2
|
||||
</script>
|
||||
</section>
|
||||
|
||||
<!-- No "extra" slides, since the separator can't be matched ("---" will become horizontal rulers) -->
|
||||
<section data-markdown data-separator="$x">
|
||||
<script type="text/template">
|
||||
A
|
||||
|
||||
---
|
||||
|
||||
B
|
||||
|
||||
---
|
||||
|
||||
C
|
||||
</script>
|
||||
</section>
|
||||
|
||||
<!-- Slide attributes -->
|
||||
<section data-markdown>
|
||||
<script type="text/template">
|
||||
<!-- .slide: data-background="#000000" -->
|
||||
## Slide attributes
|
||||
</script>
|
||||
</section>
|
||||
|
||||
<!-- Element attributes -->
|
||||
<section data-markdown>
|
||||
<script type="text/template">
|
||||
## Element attributes
|
||||
- Item 1 <!-- .element: class="fragment" data-fragment-index="2" -->
|
||||
- Item 2 <!-- .element: class="fragment" data-fragment-index="1" -->
|
||||
</script>
|
||||
</section>
|
||||
|
||||
<!-- Code -->
|
||||
<section data-markdown>
|
||||
<script type="text/template">
|
||||
```php [1|3-5]
|
||||
public function foo()
|
||||
{
|
||||
$foo = array(
|
||||
'bar' => 'bar'
|
||||
)
|
||||
}
|
||||
```
|
||||
</script>
|
||||
</section>
|
||||
|
||||
<!-- add optional line count offset, in this case 287 -->
|
||||
<section data-markdown>
|
||||
<script type="text/template">
|
||||
## echo.c
|
||||
|
||||
```c [287: 2|4,6]
|
||||
/* All of the options in this arg are valid, so handle them. */
|
||||
p = arg + 1;
|
||||
do {
|
||||
if (*p == 'n')
|
||||
nflag = 0;
|
||||
if (*p == 'e')
|
||||
eflag = '\\';
|
||||
} while (*++p);
|
||||
```
|
||||
[source](https://git.busybox.net/busybox/tree/coreutils/echo.c?h=1_36_stable#n287)
|
||||
</script>
|
||||
</section>
|
||||
|
||||
<!-- Images -->
|
||||
<section data-markdown>
|
||||
<script type="text/template">
|
||||
|
||||
</script>
|
||||
</section>
|
||||
|
||||
<!-- Math -->
|
||||
<section data-markdown>
|
||||
## The Lorenz Equations
|
||||
`\[\begin{aligned}
|
||||
\dot{x} & = \sigma(y-x) \\
|
||||
\dot{y} & = \rho x - y - xz \\
|
||||
\dot{z} & = -\beta z + xy
|
||||
\end{aligned} \]`
|
||||
</section>
|
||||
<section style="text-align: left;" data-markdown="markdown.md" data-separator="---" data-separator-vertical="^\n\n"></section>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
@@ -147,6 +33,8 @@
|
||||
<script>
|
||||
|
||||
Reveal.initialize({
|
||||
width: 1920,
|
||||
height: 1080,
|
||||
controls: true,
|
||||
progress: true,
|
||||
history: true,
|
||||
|
||||
@@ -1,41 +1,153 @@
|
||||
# Markdown Demo
|
||||
# JSONite: High-Performance Embedded Database for Semi-Structured Data
|
||||
|
||||
---
|
||||
|
||||
## The JSON Performance Crisis
|
||||
|
||||
**JSON is Everywhere:**
|
||||
- Web APIS, IoT, logs, configurations
|
||||
- Semi-structured, flexible, human-readable
|
||||
|
||||
**But Current Solutions Fail:**
|
||||
- **Large Databases**: People use MongoDB or PostgreSQL's JSONB to store data
|
||||
- **Embeded Databases**: RocksDB and PoloDB lack of ACID and SQL support
|
||||
- **Serialization to String**: Or serialize JSON into strings and store in SQLite
|
||||
|
||||
|
||||
Serialized JSON with SQL example
|
||||
|
||||
## External 1.1
|
||||
```sql
|
||||
insert into http_request_log (ip, headers)
|
||||
values ('127.0.0.1', '{
|
||||
"Content-Type": "application/oct-stream",
|
||||
"X-Forwarded-For": "100.64.0.1",
|
||||
}');
|
||||
```
|
||||
|
||||
Content 1.1
|
||||
---
|
||||
|
||||
Note: This will only appear in the speaker notes window.
|
||||
## Introducing JSONite
|
||||
|
||||
**Best of Both Worlds:**
|
||||
- SQLite's based
|
||||
- Native JSON optimization
|
||||
|
||||
**Key Advantages:**
|
||||
- ✅ ACID compliance
|
||||
- ✅ SQL simplicity
|
||||
- ✅ Serverless C library
|
||||
- ✅ Lightning-fast JSON access
|
||||
|
||||
---
|
||||
|
||||
## Smart Key Optimization
|
||||
|
||||
**Key Sorting by Length:**
|
||||
```
|
||||
{
|
||||
"id": 1,
|
||||
"address": {...}
|
||||
"name": "John",
|
||||
"email": "john@example.com",
|
||||
}
|
||||
```
|
||||
|
||||
**Sorted as:**
|
||||
```
|
||||
{
|
||||
"id", (2 chars)
|
||||
"name", (4 chars)
|
||||
"email", (5 chars)
|
||||
"address", (7 chars)
|
||||
}
|
||||
```
|
||||
|
||||
**Binary search on length → Fast lookups**
|
||||
|
||||
---
|
||||
|
||||
## Handling Massive Data: Smart TOAST
|
||||
|
||||
**The Oversized-Attribute Storage Technique**
|
||||
- Standard approach: arbitrary chunking
|
||||
- JSONite's innovation: **Data-Type Aware TOAST**
|
||||
|
||||
**Intelligent Chunking:**
|
||||
- Arrays split between elements
|
||||
- Objects split between key-value pairs
|
||||
- Text falls back to fixed chunks
|
||||
|
||||
**Enables "Slice Detoasting":**
|
||||
- `$.logs[1000000:1000010]` fetches only 10 elements
|
||||
- Not the entire multi-gigabyte array
|
||||
|
||||
|
||||
## External 1.2
|
||||
Smart Chunking Example
|
||||
|
||||
Content 1.2
|
||||
```json
|
||||
{
|
||||
"id": 1,
|
||||
"title": "some text",
|
||||
"html": <pointer to TOAST of 200k text>,
|
||||
"photos": [<pointer to TOAST of binary data>],
|
||||
"crawl_logs": [<pointer to TOAST of array of texts>]
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Query Power
|
||||
|
||||
## External 2
|
||||
**Full SQL + JSON Support:**
|
||||
- PostgreSQL-compatible JSONB path operators
|
||||
- GIN indexes for instant search
|
||||
|
||||
Content 2.1
|
||||
```sql
|
||||
SELECT *
|
||||
FROM accounts
|
||||
WHERE data @> '{"status": "active"}'
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Performance Validation: Benchmark Datasets
|
||||
|
||||
## External 3.1
|
||||
**Three Specialized Workloads:**
|
||||
|
||||
Content 3.1
|
||||
1. **YCSB-Style Read Benchmark**
|
||||
- Yahoo! Cloud Serving Benchmark
|
||||
- 1M JSON documents (1KB-100KB each)
|
||||
|
||||
2. **TPC-C Inspired Update Benchmark**
|
||||
- Transaction Processing Performance Council
|
||||
- 100K transactional JSON records
|
||||
- Frequent small field updates
|
||||
|
||||
## External 3.2
|
||||
3. **Large-Array Slice Benchmark**
|
||||
- Multi-gigabyte JSON documents
|
||||
- Massive arrays (10M+ elements)
|
||||
|
||||
Content 3.2
|
||||
**Comparison Targets:** SQLite JSONB vs MongoDB vs PostgreSQL vs JSONite
|
||||
|
||||
---
|
||||
|
||||
## External 3.3 (Image)
|
||||
## JSONite: The Future of Embedded Data Storage
|
||||
|
||||
|
||||
**Why It Matters Today:**
|
||||
- **Edge Computing**: Lightweight, handles sensor data efficiently
|
||||
- **Modern Apps**: SQL power + JSON flexibility, no schema migrations
|
||||
|
||||
**The Vision:**
|
||||
- Open source implementation
|
||||
- Community-driven development
|
||||
- Becoming the default choice for embedded JSON storage
|
||||
- Bridging SQL reliability with NoSQL flexibility
|
||||
|
||||
## External 3.4 (Math)
|
||||
---
|
||||
|
||||
`\[ J(\theta_0,\theta_1) = \sum_{i=0} \]`
|
||||
## Thank You
|
||||
|
||||
**Questions?**
|
||||
|
||||
*CHEN Yongyuan*
|
||||
*2025-11-01*
|
||||
|
||||
Reference in New Issue
Block a user