Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

关于延时消息的实现，延时消息随机读message log 影响会有多大啊？ #13

Closed
Ah39 opened this issue Dec 12, 2018 · 5 comments
Closed

关于延时消息的实现，延时消息随机读message log 影响会有多大啊？ #13

Ah39 opened this issue Dec 12, 2018 · 5 comments
Assignees
@keliwang

Comments

@Ah39
Copy link

Ah39 commented Dec 12, 2018

延时时间轮，扫描message log ，是很大范围的随机读，这个有影响吗？
最近也在做类似的事情，像了解一下
@yuyijq
Copy link
Contributor

yuyijq commented Dec 12, 2018

@Ah39

延迟消息不扫message log的

@yuyijq yuyijq closed this as completed Dec 13, 2018
@Ah39
Copy link
Author

Ah39 commented Dec 13, 2018

你原始的消息内容存储在哪里？？

@Ah39
Copy link
Author

Ah39 commented Dec 13, 2018

shedule log 直接存储消息内容吗？？

@yuyijq
Copy link
Contributor

yuyijq commented Dec 13, 2018

@Ah39 schedule log里存储了消息内容，我补充了一下文档 架构概览

@wangcn
Copy link

wangcn commented Mar 26, 2021

“第二层在内存中，当消息的投递时间即将到来的时候，会将这个小时的消息索引(索引包括消息在schedule log中的offset和size)从磁盘文件加载到内存中的hash wheel上”

根据文档里的这段话，从内存时间轮里投递消息时，难道不会频繁随机读取schedule log里的消息内容吗？

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@keliwang keliwang

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@yuyijq @keliwang @Ah39 @wangcn