[U] Update channel content
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="zh-cn">
|
||||
<id>https://aza.moe/life</id>
|
||||
<title>小桂桂的回忆录 📒</title>
|
||||
<updated>2024-11-21T18:10:53.052699+00:00</updated>
|
||||
<updated>2024-11-21T20:11:10.520499+00:00</updated>
|
||||
<link href="https://aza.moe/life" rel="alternate"/>
|
||||
<generator uri="https://lkiesow.github.io/python-feedgen" version="0.9.0">python-feedgen</generator>
|
||||
<logo>https://aza.moe/meru_256px.png</logo>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@@ -63975,7 +63975,7 @@
|
||||
"id": 4661,
|
||||
"date": "2024-11-18T04:58:09",
|
||||
"text": "(前情提要:syama 想让 gpt4o 画一张我和她和瑞希躺在床上的样子,但是输出结果一直被 OpenAI 的内容政策拦截,所以我把 prompt 拿给 FLUX 1.1 Pro Ultra 画了\n\n感觉 OpenAI 对图片生成的内容拦截是不是太严了 <i class=\"custom-emoji\" emoji-src=\"emoji/6170424195260877091.webm\">🤗</i>",
|
||||
"views": 100,
|
||||
"views": 104,
|
||||
"forwards": 1,
|
||||
"reply": {
|
||||
"id": 4659,
|
||||
@@ -63999,7 +63999,7 @@
|
||||
"id": 4662,
|
||||
"date": "2024-11-18T07:04:50",
|
||||
"text": "<a href=\"##戴上耳机\">#戴上耳机</a>\n\n看到某频道里面发了 Flamingo 突然想到这首歌 qwq\n\n♪ Black, white, green or blue\n♪ show off your natural hue\n♪ Flamingo oh oh oh woah\n♪ If you're multicoloured that’s cool too\n♪ You don’t need to change\n♪ It’s boring being the same\n♪ Flamingo oh oh oh woah\n♪ You’re pretty either way",
|
||||
"views": 86,
|
||||
"views": 92,
|
||||
"forwards": 0,
|
||||
"files": [
|
||||
{
|
||||
@@ -64156,7 +64156,7 @@
|
||||
"id": 4670,
|
||||
"date": "2024-11-20T15:44:45",
|
||||
"text": "呜呜 当时写 AquaDX 的时候选择了「先用最方便快捷的方式把网页做出来,等有问题的时候再优化」,然后就随手写出了一个请求需要把数据库两个表完整拉下来的代码 <i class=\"custom-emoji\" emoji-src=\"emoji/6323267916523374069.webp\">🥺</i>\n\n然后现在真的有问题了,现在请求一次排行榜要拉 1452 个用户和 221448 条游玩记录... 优化之前要整整 30 秒,稍微加了缓存和 batching 优化了一下也依然要十秒 <i class=\"custom-emoji\" emoji-src=\"emoji/6323582802050680516.webp\">🛌</i>",
|
||||
"views": 64,
|
||||
"views": 65,
|
||||
"forwards": 0,
|
||||
"reply": {
|
||||
"id": 3430,
|
||||
@@ -64180,7 +64180,7 @@
|
||||
"id": 4671,
|
||||
"date": "2024-11-21T03:25:16",
|
||||
"text": "今天花了一整天调查这个数据库问题, Hibernate 全责 <i class=\"custom-emoji\" emoji-src=\"emoji/6323582802050680516.webp\">🛌</i> 以后的项目再也不用 Java EE 了\n\n我试了一下把这整个函数用 native mysql 写出来,发现这条大查询只用 1.19 秒,那为什么我的 kotlin 代码运行速度差这么大呢?\n\n开了 SQL debug 之后我发现即使只是 .findAll() 都要 N 条查询,按理来说 select * from table 只要一条查询就行啊,为什么呢?仔细看看这 N 条查询发现它把 OneToOne fk 都一个一个拉下来了。原本首先花了一条查询 SELECT * FROM parent,然后又花了 N 条查询拉 SELECT * FROM child WHERE id=i...\n\n查了一下这个问题,网上说开 Hibernate bytecode enhance 就好了,它会修改编译完的字节码让 fk 链接用到的时候再查询而不是预先把所有东西查询好。问题是它不太兼容 kotlin,绕过了三个不同的问题才成功编译,之后加上 lazy fetch 终于可以让它在用到 fk 的时候再拉数据了... \n\n但是即使这样依然要把需要拉所有 fk 数据的地方改成手动 mysql 查询,因为 orm/jpql 没办法让 findAll 把单独的查询优化成 join <i class=\"custom-emoji\" emoji-src=\"emoji/6323582802050680516.webp\">🛌</i>\n\n唉 感觉凡是透明一点的 ORM 比如 ktorm 或者 exposed 都不会有这样的问题,以后不会再用 Java EE 了",
|
||||
"views": 61,
|
||||
"views": 62,
|
||||
"forwards": 0,
|
||||
"media_group_id": 13857276129125749,
|
||||
"images": [
|
||||
@@ -64214,7 +64214,7 @@
|
||||
"id": 4673,
|
||||
"date": "2024-11-21T15:30:32",
|
||||
"text": "蜂蜜太久没用变成糖块了 <i class=\"custom-emoji\" emoji-src=\"emoji/6323564771777972671.webp\">🤤</i>",
|
||||
"views": 49,
|
||||
"views": 52,
|
||||
"forwards": 0,
|
||||
"images": [
|
||||
{
|
||||
@@ -64233,7 +64233,7 @@
|
||||
"id": 4674,
|
||||
"date": "2024-11-21T17:55:52",
|
||||
"text": "用原生 mysql 重写了整个查询之后获取排行榜从 30s 降到 4s 了!\n\n<del>果然什么优化都没有 RIIR 最方便</del> <i class=\"custom-emoji\" emoji-src=\"emoji/6170432338518869955.webm\">🦀</i>",
|
||||
"views": 16,
|
||||
"views": 28,
|
||||
"forwards": 0,
|
||||
"reply": {
|
||||
"id": 4670,
|
||||
|
||||
@@ -12,7 +12,7 @@
|
||||
<link>https://aza.moe/life</link>
|
||||
</image>
|
||||
<language>zh-cn</language>
|
||||
<lastBuildDate>Thu, 21 Nov 2024 18:10:53 +0000</lastBuildDate>
|
||||
<lastBuildDate>Thu, 21 Nov 2024 20:11:10 +0000</lastBuildDate>
|
||||
<item>
|
||||
<title>小桂桂的回忆录 📒 #4674</title>
|
||||
<link>https://aza.moe/life?post=4674</link>
|
||||
|
||||
Reference in New Issue
Block a user