Mercurial > prosody-modules
view mod_log_events_by_cpu_usage/mod_log_events_by_cpu_usage.lua @ 4688:05725276fac0
mod_bookmarks2: Use same default as mod_pep for max_items
Should fix the issue with max items until the proper "max" can be used,
by following the configured max.
While "max" is already in trunk, it's not easily usable in 0.11.x
This limit and option was added to mod_pep in Prosody rev aefb96a52f5f
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Wed, 15 Sep 2021 17:39:37 +0200 |
parents | c0bc97c0ba61 |
children |
line wrap: on
line source
module:set_global(); local treshold = module:get_option_number("log_cpu_threshold", 0.01); function event_wrapper(handlers, event_name, event_data) local cpu_before = os.clock(); local ret = handlers(event_name, event_data); local cpu_after = os.clock(); if (cpu_after - cpu_before) > treshold then module:log("warn", "%g seconds of CPU usage while processing event '%s'", (cpu_after - cpu_before), event_name); end return ret; end local http_events = require "net.http.server"._events; module:wrap_object_event(http_events, false, event_wrapper); module:wrap_event(false, event_wrapper); function module.add_host(module) module:wrap_event(false, event_wrapper); end