15 Commits (b750fb27b0f20e9443827732b69a504a76036430)

Author	SHA1	Message	Date
moneromooo-monero	93c59b29a8	perf_timer: check allowed categories before logging	6 years ago
moneromooo-monero	6a507dab6f	perf_timer: add a way to get and reset the current time	6 years ago
moneromooo-monero	c1581a5bb8	perf_timer: only log to file	6 years ago
Riccardo Spagni	0cc3fc3756	Merge pull request #4769 ... 5808530f blockchain: remove unused output_scan_worker parameter (moneromooo-monero) 1426209a blockchain: don't run threads if we have just one function to run (moneromooo-monero) 6f7a5fd4 db_lmdb: slight speedup getting array data from the blockchain (moneromooo-monero) 99fbe100 db_lmdb: save some string copies for readonly db keys/values (moneromooo-monero) bf31447e tx_pool: speed up take_tx for transactions from blocks (moneromooo-monero) 4f005a77 tx_pool: remove unnecessary get_transaction_hash (moneromooo-monero) 593ef598 perf_timer: call reserve on new timer array (moneromooo-monero) 6ecc99ad core: avoid unnecessary tx/blob conversions (moneromooo-monero) 00cc1a16 unit_tests: notify test special case for the usual weirdo (moneromooo-monero)	6 years ago
moneromooo-monero	593ef5981d	perf_timer: call reserve on new timer array ... to avoid reallocations in the vast majority of the time	6 years ago
moneromooo-monero	ca9b996dcb	perf_timer: separate log categories based on caller categories ... Also default to microseconds, for homogeneity Makes it easier to enable what we need	6 years ago
moneromooo-monero	7314d919e7	perf_timer: split timer class into a base one and a logging one	6 years ago
moneromooo-monero	f3f7da624d	perf_timer: rewrite to make it clear there is no division by zero ... It could have happened if epee::misc_utils::get_ns_count is buggy, at a push Coverity 182561	6 years ago
Riccardo Spagni	4c302c6385	Merge pull request #3120 ... 6cf56682 perf_timer: add faster x86_64 timers, and pause/resume (moneromooo-monero) 411da337 perf_timer: use std::unique_ptr instead of new/delete (moneromooo-monero)	7 years ago
xmr-eric	84a7f6a482	Readd copyright starting date	7 years ago
xmr-eric	18216f19dd	Update 2018 copyright	7 years ago
moneromooo-monero	6cf56682bc	perf_timer: add faster x86_64 timers, and pause/resume	7 years ago
moneromooo-monero	09ce03d612	move includes around to lessen overall load	7 years ago
moneromooo-monero	5833d66f65	Change logging to easylogging++ ... This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=*:FATAL This one is very verbose: MONERO_LOGS=*:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=*:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net* logs only at INFO: MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels.	8 years ago
moneromooo-monero	74dfdb0b30	perf_timer: new class and macros to make performance logs easier ... Call PERF_TIMER(name), which is scoped.	8 years ago