BGM

TV动画《期待在地下城邂逅有错吗 Ⅳ 深章 灾厄篇》片尾曲 切り傷
歌手：sajou no hana

<audio controls> <source src="http://music.163.com/song/media/outer/url?id=2024541034.mp3" type="audio/mpeg"> Your browser does not support the audio element. </audio>

感想

地错第四季也终于完结啦，新番里最好看的，不枉我每周四蹲首播啃生肉看完，这一季完完整整的把小说第14卷全部一次性讲完啦，完全是琉主场，琉的过去，眷族团灭的原因以及琉内心的变化，

最后也终于释怀了自己的过去，找到了属于自己的正义! 加入白兔后宫团（不是

不得不给节操社(J.C.STAFF)点个赞，还是保持了一贯的高制作水准，没有特别的崩坏，这一季看下来不管是剧情节奏还是画面音乐都非常棒！果然很喜欢这种王道的剧情啊，男孩与女孩的相遇，互相拯救的故事什么的，真是太棒了！

最后一幕琉的笑容真的太 太 太好看啦！

最近也把新的18卷小说看完了，白兔终于也到level5了，女神芙蕾雅线故事的高潮阶段也终于全部讲完，最后琉Level6救场的场景太帅啦！最后还直球告白贝尔！我宣布，琉股暴涨！诸君，我喜欢elf！

最后

外传剑姬神圣谭13 14卷貌似也快出了，看来大森真的想把每一个地错的角色魅力和眷族故事都展示出来，大森你给点力，学学某河马打字机，多出点！孩子爱看！

工具下载地址：

stable-diffusion-webui (推荐)

1.下载完成后运行webui-user.bat文件，会下载相关的依赖，国内网络可能需要翻墙或者用镜像站(修改launch.py文件把github地址都改为国内的镜像站地址)，也可以推荐dev-sidecar这个免费工具加速github。 或者可以直接上b站检索秋葉aaakiup主，直接下载整合包,再或者直接下载第三方客户端

2.安装完成后再运行webui-user.bat文件后等待出现Running on local URL: http://127.0.0.1:7860 就可以访问127.0.0.1:7860打开webui页面啦。

3.打开后先别急，需要安装一些基础的插件，点击扩展，从网址安装，然后把git地址粘贴后安装即可，我这边推荐几个最常用的：

汉化插件 安装完后：setting >> user interface >> Localization (requires restart) >> 选择 zh-CN >> apply setting >> reload ui

Control插件 用来加载lora相关模型。

关键字补全插件 用来补全prompt关键字的，适合英文小白~

4.安装完成后到设置里的显示所有页面，快捷设置列表填写sd_model_checkpoint,sd_vae然后重启webui，基础工具就安装好啦，接下来就是模型了！

模型下载地址：

Civitai

1.注册好账号后就可以查看很多网上分享的模型，找一个你最喜欢的，例如Counterfeit，点击下载即可。

2.下载好后记得要把模型放到 \webui\models\Stable-diffusion 目录下，这样才会读取到模型，Lora的模型要放到\webui\models\Lora里,有模型后就可以生成AI图片啦！

当然只是简单的模型还是不够的，后续进阶还需要用到vae模型，EasyNegative模型，lora模型，openpose模型，高清化等，这个后续有时间再梳理下，慢慢学习进步！

分享例子：

关键字： ((masterpiece,best quality)),1girl, solo, animal ears, rabbit, barefoot, knees up, dress, sitting, rabbit ears, short sleeves, looking at viewer, grass, short hair, smile, white hair, puffy sleeves, outdoors, puffy short sleeves, bangs, on ground, full body, animal, white dress, sunlight, brown eyes, dappled sunlight, day, depth of field

Negative关键字： EasyNegative, extra fingers,fewer fingers,

Steps: 20, Sampler: DPM++ 2M Karras, CFG scale: 10, Seed: 414619472, Size: 512x728, Model hash: 59ea4aa1d8, Model: cetusMix_cetusVersion3, Denoising strength: 0.7, Hires upscale: 2, Hires steps: 20, Hires upscaler: SwinIR_4x

An h1 header

Paragraphs are separated by a blank line.

2nd paragraph. Italic, bold, and monospace. Itemized lists look like:

• this one
• that one
• the other one

Note that --- not considering the asterisk --- the actual text content starts at 4-columns in.

Block quotes are written like so.

They can span multiple paragraphs, if you like.

Use 3 dashes for an em-dash. Use 2 dashes for ranges (ex., "it's all in chapters 12--14"). Three dots ... will be converted to an ellipsis. Unicode is supported. ☺

An h2 header

Here's a numbered list:

1. first item
2. second item
3. third item

Note again how the actual text starts at 4 columns in (4 characters from the left side). Here's a code sample:

# Let me re-iterate ...
for i in 1 .. 10 { do-something(i) }

As you probably guessed, indented 4 spaces. By the way, instead of indenting the block, you can use delimited blocks, if you like:

define foobar() {
    print "Welcome to flavor country!";
}

(which makes copying & pasting easier). You can optionally mark the delimited block for Pandoc to syntax highlight it:

import time
# Quick, count to ten!
for i in range(10):
    # (but not *too* quick)
    time.sleep(0.5)
    print i

An h3 header

Now a nested list:

1. First, get these ingredients:

   • carrots
   • celery
   • lentils

2. Boil some water.

3. Dump everything in the pot and follow this algorithm:

    find wooden spoon
    unimage pot
    stir
    image pot
    balance wooden spoon precariously on pot handle
    wait 10 minutes
    goto first step (or shut off burner when done)
   

   Do not bump wooden spoon or it will fall.

Notice again how text always lines up on 4-space indents (including that last line which continues item 3 above).

Here's a link to a website, to a local doc, and to a section heading in the current doc. Here's a footnote [^1].

[^1]: Footnote text goes here.

Tables can look like this:

size material color

9 leather brown 10 hemp canvas natural 11 glass transparent

Table: Shoes, their sizes, and what they're made of

(The above is the caption for the table.) Pandoc also supports multi-line tables:

keyword text

red Sunsets, apples, and other red or reddish things.

green Leaves, grass, frogs and other things it's not easy being.

A horizontal rule follows.

Here's a definition list:

apples : Good for making applesauce. oranges : Citrus! tomatoes : There's no "e" in tomatoe.

Again, text is indented 4 spaces. (Put a blank line between each term/definition pair to spread things out more.)

Here's a "line block":

| Line one | Line too | Line tree

and images can be specified like so:

Inline math equations go in like so: $\omega = d\phi / dt$. Display math should get its own line and be put in in double-dollarsigns:

$$I = \int \rho R^{2} dV$$

And note that you can backslash-escape any punctuation characters which you wish to be displayed literally, ex.: `foo`, *bar*, etc.

image image source: Source

This blog template is built with Astro. For the things that are not mentioned in this guide, you may find the answers in the Astro Docs.

Front-matter of Posts

---
title: My First Blog Post
published: 2023-09-09
description: This is the first post of my new Astro blog.
image: ./image.jpg
tags: [Foo, Bar]
category: Front-end
draft: false
---

Where to Place the Post Files

Your post files should be placed in src/content/posts/ directory. You can also create sub-directories to better organize your posts and assets.

src/content/posts/
├── post-1.md
└── post-2/
    ├── image.png
    └── index.md

An h1 header

Paragraphs are separated by a blank line.

2nd paragraph. Italic, bold, and monospace. Itemized lists look like:

• this one
• that one
• the other one

Note that --- not considering the asterisk --- the actual text content starts at 4-columns in.

Block quotes are written like so.

They can span multiple paragraphs, if you like.

Use 3 dashes for an em-dash. Use 2 dashes for ranges (ex., "it's all in chapters 12--14"). Three dots ... will be converted to an ellipsis. Unicode is supported. ☺

An h2 header

Here's a numbered list:

1. first item
2. second item
3. third item

Note again how the actual text starts at 4 columns in (4 characters from the left side). Here's a code sample:

# Let me re-iterate ...
for i in 1 .. 10 { do-something(i) }

As you probably guessed, indented 4 spaces. By the way, instead of indenting the block, you can use delimited blocks, if you like:

define foobar() {
    print "Welcome to flavor country!";
}

(which makes copying & pasting easier). You can optionally mark the delimited block for Pandoc to syntax highlight it:

import time
# Quick, count to ten!
for i in range(10):
    # (but not *too* quick)
    time.sleep(0.5)
    print i

An h3 header

Now a nested list:

1. First, get these ingredients:

   • carrots
   • celery
   • lentils

2. Boil some water.

3. Dump everything in the pot and follow this algorithm:

    find wooden spoon
    uncover pot
    stir
    cover pot
    balance wooden spoon precariously on pot handle
    wait 10 minutes
    goto first step (or shut off burner when done)
   

   Do not bump wooden spoon or it will fall.

Notice again how text always lines up on 4-space indents (including that last line which continues item 3 above).

Here's a link to a website, to a local doc, and to a section heading in the current doc. Here's a footnote [^1].

[^1]: Footnote text goes here.

Tables can look like this:

size material color

9 leather brown 10 hemp canvas natural 11 glass transparent

Table: Shoes, their sizes, and what they're made of

(The above is the caption for the table.) Pandoc also supports multi-line tables:

keyword text

red Sunsets, apples, and other red or reddish things.

green Leaves, grass, frogs and other things it's not easy being.

A horizontal rule follows.

Here's a definition list:

apples : Good for making applesauce. oranges : Citrus! tomatoes : There's no "e" in tomatoe.

Again, text is indented 4 spaces. (Put a blank line between each term/definition pair to spread things out more.)

Here's a "line block":

| Line one | Line too | Line tree

and images can be specified like so:

Inline math equations go in like so: $\omega = d\phi / dt$. Display math should get its own line and be put in in double-dollarsigns:

$$I = \int \rho R^{2} dV$$

And note that you can backslash-escape any punctuation characters which you wish to be displayed literally, ex.: `foo`, *bar*, etc.

简介

    影响ClickHouse查询性能的因素很多。在大多数情况下，关键因素是ClickHouse在计算查询WHERE子句条件时是否可以使用主键。因此，选择适用于最常见查询模式的主键对于有效的表设计至关重要。     用户通常依赖ClickHouse获取时间序列类型的数据，但他们通常希望根据其他业务维度(如客户id、网站URL或产品编号)分析相同的数据。在这种情况下，查询性能可能会相当差，因为可能需要对每个列值进行完整扫描才能应用WHERE子句条件。虽然ClickHouse在这些情况下仍然相对较快，但评估数百万或数十亿个单独的值将导致“非索引”查询的执行速度比基于主键的查询慢得多。     ClickHouse提供了一种不同类型的索引，在特定情况下可以显著提高查询速度。这些结构被标记为“跳过(Skip)”索引，因为它们使ClickHouse能够跳过读取保证没有匹配值的重要数据块。

介绍

Clickhouse索引的特点为: 排序索引+稀疏索引+列式存储, 因此相应的Clickhouse最合适的场景就是基于排序字段的范围过滤后的聚合查询。

因为排序索引, 所有基于排序字段的查询会明显由于MR类型计算, 否则Hive/Spark这类动态资源的更优 由于稀疏索引, 点查询的效率可能没有KV型数据库高, 因此适合相对大范围的过滤条件 因为列式存储, 数据压缩率高, 对应做聚合查询效率也会更高.

实践

因为表索引不好在创建表后再进行创建，所以最好在创建表的时候就计划好并创建，例如cloki的表主要是samples_v3和time_series_gin表是用作主要查询。
对于cloki.time_series_gin表：
对key列进行索引：ALTER TABLE cloki.time_series_gin_ ADD INDEX idx_key(key) TYPE minmax GRANULARITY 8192;
对val列进行索引：ALTER TABLE cloki.time_series_gin_ ADD INDEX idx_val(val) TYPE minmax GRANULARITY 8192;
对fingerprint列进行索引：ALTER TABLE cloki.time_series_gin_ ADD INDEX idx_fingerprint(fingerprint) TYPE minmax GRANULARITY 8192;

对于cloki.samples_v3表：
对timestamp_ns列进行索引：ALTER TABLE cloki.samples_v3_ ADD INDEX idx_timestamp_ns(timestamp_ns) TYPE minmax GRANULARITY 8192;
对fingerprint列进行索引：ALTER TABLE cloki.samples_v3_ ADD INDEX idx_fingerprint(fingerprint) TYPE minmax GRANULARITY 8192;
对string列进行索引：ALTER TABLE cloki.samples_v3_ ADD INDEX idx_string(string) TYPE minmax GRANULARITY 8192;

如果需要对已有的数据也进行索引，需要 ALTER TABLE cloki.samples_v3_ MATERIALIZE INDEX idx_timestamp_ns; 数据量较大，会非常慢。

参考

官方文档
深入浅出clickhouse-index