ballontt commented on issue #2120:
URL: https://github.com/apache/brpc/issues/2120#issuecomment-2136879471
mark
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsub
MJY-HUST commented on code in PR #2645:
URL: https://github.com/apache/brpc/pull/2645#discussion_r1618964917
##
test/bthread_key_unittest.cpp:
##
@@ -385,19 +388,21 @@ TEST(KeyTest, using_pool) {
ASSERT_EQ(0, bthread_start_urgent(&bth, &attr, pool_thread, &bth_data));
lorinlee commented on issue #2653:
URL: https://github.com/apache/brpc/issues/2653#issuecomment-2137649026
这里“作为指标暴露出去”是指期望怎么暴露？使用场景的话，比如可以用builtin service看这个bvar，访问
http://ip:internal_port/vars/process_username 就可以看到这个bvar对应的值。
--
This is an automated message from the Apache Git Service.
lorinlee commented on issue #2652:
URL: https://github.com/apache/brpc/issues/2652#issuecomment-2137705599
目前是生产环境遇到了什么问题吗？
依赖管理角度的话，确实可以支持一个编译参数关闭对leveldb的依赖。
切换rocksdb我觉得需要看看实际的遇到问题是什么，rocksdb确实比leveldb在很多地方都有优化，但也导致了它整个实现是比较复杂的，要看引入的必要性了。在rpcz这个场景我个人觉得leveldb是够用的，切换到rocksdb的
corznoc commented on issue #2652:
URL: https://github.com/apache/brpc/issues/2652#issuecomment-2137742497
用的挺好的，没有遇到问题，rocksdb我也觉得复杂了些，只是leveldb公司不让用了😀 原始邮件 发件人：
LorinLee ***@***.***>日期： 2024年5月29日周三 23:33收件人： apache/brpc ***@***.***>抄送：
corznoc ***@***.***>, Author ***@***.
chenBright commented on PR #2645:
URL: https://github.com/apache/brpc/pull/2645#issuecomment-2138550242
@wwbmmm 也看看这个PR
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To u
lorinlee commented on issue #2650:
URL: https://github.com/apache/brpc/issues/2650#issuecomment-2138558460
请问jemalloc是什么版本？NUMA配的cpu分配策略和内存分配策略是什么？另外可以开启ASAN跑一下吗，不确定是不是其他地方的内存踩坏导致这里出错
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
