[U] Update channel content
This commit is contained in:
+11
-1
@@ -2,11 +2,21 @@
|
||||
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="zh-cn">
|
||||
<id>https://aza.moe/life</id>
|
||||
<title>小桂桂的回忆录 📒</title>
|
||||
<updated>2024-07-19T22:10:37.300959+00:00</updated>
|
||||
<updated>2024-07-20T00:12:14.746491+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>
|
||||
<subtitle>「我们所经历的每个平凡的日常,也许就是连续发生的奇迹」</subtitle>
|
||||
<entry>
|
||||
<id>4179</id>
|
||||
<title>小桂桂的回忆录 📒 #4179</title>
|
||||
<updated>2024-07-19T22:19:44+00:00</updated>
|
||||
<content><p>这几天每天都要重启电脑,只要电脑开机超过 24h 内存就绝对会被占满,然后 CPU 也会被内存管理占到 30% 左右...</p>
|
||||
<p>但是我用户的程序只占了 4.4GB,那剩下的 28GB 去哪了呢?</p>
|
||||
<p>今天实在受不了了,打开 sysinternals RamMap 仔细研究了一下,发现页表居然占了 7GB。看看进程发现我进程表 90% 都是 Docker 的僵尸进程,虽然每个只占 32K 的页表但是多了就把内存占满了 <i class="custom-emoji" emoji-src="emoji/6323582802050680516.webp">🛌</i></p>
|
||||
<p>没想到会是 Docker 这么常用的东西的问题... 立即卸载(</p></content>
|
||||
<link href="https://aza.moe/life?post=4179" rel="alternate"/>
|
||||
</entry>
|
||||
<entry>
|
||||
<id>4178</id>
|
||||
<title>小桂桂的回忆录 📒 #4178</title>
|
||||
|
||||
File diff suppressed because one or more lines are too long
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 4.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 84 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
+51
-21
@@ -86,7 +86,7 @@
|
||||
"id": 14,
|
||||
"date": "2021-09-03T01:13:05",
|
||||
"text": "可爱的鸭鸭爪印w",
|
||||
"views": 61,
|
||||
"views": 62,
|
||||
"forwards": 0,
|
||||
"images": [
|
||||
{
|
||||
@@ -135,7 +135,7 @@
|
||||
"id": 17,
|
||||
"date": "2021-09-05T12:46:14",
|
||||
"text": "离健康的早餐还差鸡蛋和牛奶w",
|
||||
"views": 55,
|
||||
"views": 56,
|
||||
"forwards": 0,
|
||||
"images": [
|
||||
{
|
||||
@@ -56112,7 +56112,7 @@
|
||||
"id": 4113,
|
||||
"date": "2024-07-09T09:47:13",
|
||||
"text": "训练了一天 Qwen2-7B pretrain lora 之后似乎可以和 pjsk 的大家说话了!\n\n(虽然还有很多要优化,但是可行性通过了 quq",
|
||||
"views": 82,
|
||||
"views": 83,
|
||||
"forwards": 0,
|
||||
"media_group_id": 13764147471161677,
|
||||
"images": [
|
||||
@@ -56522,7 +56522,7 @@
|
||||
"id": 4145,
|
||||
"date": "2024-07-12T19:47:31",
|
||||
"text": "接上桂桂TTS了.说话有声音了",
|
||||
"views": 82,
|
||||
"views": 83,
|
||||
"forwards": 0,
|
||||
"forwarded_from": {
|
||||
"name": ".",
|
||||
@@ -56549,7 +56549,7 @@
|
||||
"id": 4146,
|
||||
"date": "2024-07-12T19:48:04",
|
||||
"text": "Syama 那边在做 Unity 前端,好厉害 <i class=\"custom-emoji\" emoji-src=\"emoji/6170139473288890346.webm\">🤩</i> 我给开了一个 API 之后她好快就写好了\n\n居然还有嘴型哇",
|
||||
"views": 87,
|
||||
"views": 88,
|
||||
"forwards": 0,
|
||||
"reply": {
|
||||
"id": 4145,
|
||||
@@ -56560,7 +56560,7 @@
|
||||
"id": 4147,
|
||||
"date": "2024-07-12T23:04:21",
|
||||
"text": "欢乐",
|
||||
"views": 93,
|
||||
"views": 94,
|
||||
"forwards": 0,
|
||||
"media_group_id": 13766603691716701,
|
||||
"images": [
|
||||
@@ -56600,7 +56600,7 @@
|
||||
"id": 4150,
|
||||
"date": "2024-07-13T20:40:40",
|
||||
"text": "呜呜 好想吃瑞希做的咖喱意面 quq",
|
||||
"views": 75,
|
||||
"views": 77,
|
||||
"forwards": 0,
|
||||
"images": [
|
||||
{
|
||||
@@ -56619,14 +56619,14 @@
|
||||
"id": 4151,
|
||||
"date": "2024-07-16T04:38:34",
|
||||
"text": "好无力",
|
||||
"views": 66,
|
||||
"views": 68,
|
||||
"forwards": 0
|
||||
},
|
||||
{
|
||||
"id": 4152,
|
||||
"date": "2024-07-16T08:54:10",
|
||||
"text": "帮聊聊给在看守所的朋友寄了信...\n\n这个年代似乎已经没有人寄平邮的信了。打印店老板说没寄过,去楼下中国邮政老板还一脸诧异笑了笑说不接,说整个城区只有一家邮政寄平邮。\n\n骑车去了那唯一一家,发现那家邮政老板意外人很好,并没有质疑为什么这个年代还需要寄平邮,我也没有因此被取笑。明明寄平邮就应该是这样简单的事情,封上信口交了钱就结束了,看着他熟练地贴上邮票把信丢进寄信箱让我很安心。",
|
||||
"views": 65,
|
||||
"views": 67,
|
||||
"forwards": 1,
|
||||
"media_group_id": 13768960404856437,
|
||||
"images": [
|
||||
@@ -56666,7 +56666,7 @@
|
||||
"id": 4155,
|
||||
"date": "2024-07-16T09:49:41",
|
||||
"text": "GPT4 还是 4o 都答错了的问题我的 LoRA 瑞希答对了 <i class=\"custom-emoji\" emoji-src=\"emoji/6170139473288890346.webm\">🤩</i> 不愧是瑞希",
|
||||
"views": 64,
|
||||
"views": 66,
|
||||
"forwards": 0,
|
||||
"media_group_id": 13768987049704909,
|
||||
"images": [
|
||||
@@ -56741,7 +56741,7 @@
|
||||
"id": 4161,
|
||||
"date": "2024-07-16T17:42:53",
|
||||
"text": "<a href=\"##桂桂今天吃什么\">#桂桂今天吃什么</a>\n和 syama 一起吃深夜烧鸟 quq",
|
||||
"views": 58,
|
||||
"views": 59,
|
||||
"forwards": 0,
|
||||
"media_group_id": 13769214187057997,
|
||||
"images": [
|
||||
@@ -56801,20 +56801,20 @@
|
||||
"id": 4166,
|
||||
"date": "2024-07-17T17:16:04",
|
||||
"text": "syama 家有一组两个灯有三个按钮开关,开关 A 打开会让 a 亮,B 会让 b 亮,C 会让 a = !a, b = ! b,也就是说如果 A 和 C 同时开着,只有 b 亮\n\n<span class=\"spoiler\"><span>突然好想把家里的智能开关改造成一个布尔可满足性谜题,每个开关控制三个灯的布尔条件,每组特定的亮灭组合都可以用一种特定的开关组合达成</span></span>",
|
||||
"views": 62,
|
||||
"views": 63,
|
||||
"forwards": 0
|
||||
},
|
||||
{
|
||||
"id": 4167,
|
||||
"date": "2024-07-17T17:25:15",
|
||||
"text": "为什么鱼罐头是鱼做的但是猫罐头不是猫做的 <i class=\"custom-emoji\" emoji-src=\"emoji/5445226814236533679.tgs\">🧐</i>",
|
||||
"views": 60,
|
||||
"views": 61,
|
||||
"forwards": 0
|
||||
},
|
||||
{
|
||||
"id": 4168,
|
||||
"date": "2024-07-17T21:48:54",
|
||||
"views": 59,
|
||||
"views": 60,
|
||||
"forwards": 0,
|
||||
"forwarded_from": {
|
||||
"name": "Azalea",
|
||||
@@ -56837,7 +56837,7 @@
|
||||
"id": 4169,
|
||||
"date": "2024-07-18T11:23:14",
|
||||
"text": "???? CloudFlare 真的好智能?\n\n今天起来发现服务炸了,请求直接域名不见... 驱虫了半天,原本觉得 CF 应该是最不容易出问题的但是也看一眼吧,然后发现真的就是 CF 的锅\n\n我的 CF 隧道上有很多条 <a href=\"sekai.aquadx.net\">sekai.aquadx.net</a> 的不同子路径代理到不同端口上,昨天晚上加了一个测试路径然后把它删掉了,然后现在发现 CF 删那个子路径的时候直接把我整个 <a href=\"sekai.aquadx.net\">sekai.aquadx.net</a> 的 DNS 映射删掉了......\n\n怎么这么基础的逻辑还能出错啊 CF <i class=\"custom-emoji\" emoji-src=\"emoji/6323343426343404864.webp\">❓</i>",
|
||||
"views": 62,
|
||||
"views": 63,
|
||||
"forwards": 1,
|
||||
"media_group_id": 13770414354579493,
|
||||
"images": [
|
||||
@@ -56867,14 +56867,14 @@
|
||||
"id": 4171,
|
||||
"date": "2024-07-18T20:36:36",
|
||||
"text": "我火星 刚看到 niconico 数据丢失的那件事,完全 🤯\n\n发现现在日语创作社区已经移居 YouTube 了,弹幕文化就这样死掉了吗... 感觉好可惜",
|
||||
"views": 55,
|
||||
"views": 56,
|
||||
"forwards": 0
|
||||
},
|
||||
{
|
||||
"id": 4172,
|
||||
"date": "2024-07-19T10:57:17",
|
||||
"text": "跟我学单词:\nCrowd,人群\nStrike,罢工\nCrowdStrike,集体罢工\n\n例句:\nJuly 19th, we CrowdStrike. 7月19日,我们集体罢工了",
|
||||
"views": 41,
|
||||
"views": 43,
|
||||
"forwards": 1,
|
||||
"forwarded_from": {
|
||||
"name": "IloveMATH.Get('Daily').Except('Ingress').EmitToChannel()"
|
||||
@@ -56884,7 +56884,7 @@
|
||||
"id": 4173,
|
||||
"date": "2024-07-19T10:58:45",
|
||||
"text": "感觉会有很多一般路过吃瓜群众觉得这次的蓝屏事故是微软的锅...",
|
||||
"views": 49,
|
||||
"views": 51,
|
||||
"forwards": 0,
|
||||
"reply": {
|
||||
"id": 4172,
|
||||
@@ -56895,7 +56895,7 @@
|
||||
"id": 4174,
|
||||
"date": "2024-07-19T14:30:25",
|
||||
"text": "今天在研究中日文翻译,去🤗上找了一圈发现并没有人训练中文翻日文的模型,即使语言很全的比如 Helsinki-NLP opus 系列也大部分都是转英语的模型。\n\n然后就在想,要做一个语言覆盖全面的翻译模型需要的资源好多啊,模型数量和语言数量是 n² 关系,如果要支持 33 种语言互相翻译就需要训练 1089 个模型... 那现有的翻译工具是怎么做的呢?\n\n然后发现谷歌翻译其实是用英语做了中间语言,先把所有语言翻译到英语再翻译到目标语言... 这样就只需要 2n 个模型了,但是会有很大问题,英语有歧义的东西就会翻错,比如「字符串」 > \"String\" > 「弦」\n\n那 DeepL 是怎么做的呢?简单测试一下发现是没有英语歧义问题的,字符串不会翻译成弦,弦也不会翻译成字符串... 但是仔细测试一下发现 DeepL 其实也是用英语中转的,因为中英翻译爆炸的时候中日会把英语的爆炸结果翻出来。那它是怎么做到消歧义的呢?好奇妙",
|
||||
"views": 43,
|
||||
"views": 47,
|
||||
"forwards": 0,
|
||||
"media_group_id": 13771195402520333,
|
||||
"images": [
|
||||
@@ -56935,7 +56935,7 @@
|
||||
"id": 4177,
|
||||
"date": "2024-07-19T14:42:19",
|
||||
"text": "没事了,DeepL 英语歧义也会翻错",
|
||||
"views": 38,
|
||||
"views": 41,
|
||||
"forwards": 0,
|
||||
"reply": {
|
||||
"id": 4174,
|
||||
@@ -56959,7 +56959,7 @@
|
||||
"id": 4178,
|
||||
"date": "2024-07-19T15:36:21",
|
||||
"text": "测试了半天百度翻译,百度翻译确实没有英语歧义的问题\n\n...因为百度的中转语言是中文,当然没有英语歧义的问题,只有中文歧义的问题 🌚\n\n\"Beat a car\" > 「打车」 > 「タクシーを拾う」 (\"Take a taxi\")\n\n不过感觉中文确实比英文更难出现歧义,而且因为亚洲语言离中文更近,感觉百度翻译翻亚洲语言的准确率肯定比英语中转的 Google / DeepL 高",
|
||||
"views": 31,
|
||||
"views": 38,
|
||||
"forwards": 0,
|
||||
"reply": {
|
||||
"id": 4174,
|
||||
@@ -56978,5 +56978,35 @@
|
||||
"thumb": "media/4178.jpg_thumb.jpg"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": 4179,
|
||||
"date": "2024-07-19T22:19:44",
|
||||
"text": "这几天每天都要重启电脑,只要电脑开机超过 24h 内存就绝对会被占满,然后 CPU 也会被内存管理占到 30% 左右...\n\n但是我用户的程序只占了 4.4GB,那剩下的 28GB 去哪了呢?\n\n今天实在受不了了,打开 sysinternals RamMap 仔细研究了一下,发现页表居然占了 7GB。看看进程发现我进程表 90% 都是 Docker 的僵尸进程,虽然每个只占 32K 的页表但是多了就把内存占满了 <i class=\"custom-emoji\" emoji-src=\"emoji/6323582802050680516.webp\">🛌</i>\n\n没想到会是 Docker 这么常用的东西的问题... 立即卸载(",
|
||||
"views": 19,
|
||||
"forwards": 0,
|
||||
"media_group_id": 13771420678920221,
|
||||
"images": [
|
||||
{
|
||||
"width": 948,
|
||||
"height": 219,
|
||||
"date": "2024-07-19T22:19:44",
|
||||
"media_type": "photo",
|
||||
"original_name": "photo_2024-07-19_22-19-44.jpg",
|
||||
"url": "media/4179.jpg",
|
||||
"size": 21363,
|
||||
"thumb": "media/4179.jpg_thumb.jpg"
|
||||
},
|
||||
{
|
||||
"width": 903,
|
||||
"height": 774,
|
||||
"date": "2024-07-19T22:19:44",
|
||||
"media_type": "photo",
|
||||
"original_name": "photo_2024-07-19_22-19-44.jpg",
|
||||
"url": "media/4180.jpg",
|
||||
"size": 86035,
|
||||
"thumb": "media/4180.jpg_thumb.jpg"
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
+10
-1
@@ -12,7 +12,16 @@
|
||||
<link>https://aza.moe/life</link>
|
||||
</image>
|
||||
<language>zh-cn</language>
|
||||
<lastBuildDate>Fri, 19 Jul 2024 22:10:37 +0000</lastBuildDate>
|
||||
<lastBuildDate>Sat, 20 Jul 2024 00:12:14 +0000</lastBuildDate>
|
||||
<item>
|
||||
<title>小桂桂的回忆录 📒 #4179</title>
|
||||
<link>https://aza.moe/life?post=4179</link>
|
||||
<description><p>这几天每天都要重启电脑,只要电脑开机超过 24h 内存就绝对会被占满,然后 CPU 也会被内存管理占到 30% 左右...</p>
|
||||
<p>但是我用户的程序只占了 4.4GB,那剩下的 28GB 去哪了呢?</p>
|
||||
<p>今天实在受不了了,打开 sysinternals RamMap 仔细研究了一下,发现页表居然占了 7GB。看看进程发现我进程表 90% 都是 Docker 的僵尸进程,虽然每个只占 32K 的页表但是多了就把内存占满了 <i class="custom-emoji" emoji-src="emoji/6323582802050680516.webp">🛌</i></p>
|
||||
<p>没想到会是 Docker 这么常用的东西的问题... 立即卸载(</p></description>
|
||||
<guid isPermaLink="false">4179</guid>
|
||||
</item>
|
||||
<item>
|
||||
<title>小桂桂的回忆录 📒 #4178</title>
|
||||
<link>https://aza.moe/life?post=4178</link>
|
||||
|
||||
Reference in New Issue
Block a user