4

The execution time is based on many factors in each execution. It could be the cache missing or process management could blocks the nodeos process and makes the execution time exceeds the max-transaction-time. The max-transaction-time set by nodeos on startup or in the config file controls the time to throw the Error 3080006. The default value is 30ms. ...


3

By default, Nodes have a config for max-transaction-time = 30 but it doesn't necessary for all Bp to have exact same config for max transaction time so they can change at any time. ::get_resource_limits() is privileged API, so it cannot be used by normal account (only privileged account can call it like eosio) You can get the limit of cpu, net or ram by the ...


2

I think, it may related with cache (as twksos commented). https://github.com/EOSIO/eos/blob/11c25394b6dd05cc3c97f0b7471a84f3d7cfbca3/libraries/chain/include/eosio/chain/wasm_interface_private.hpp#L58 auto it = instantiation_cache.find(code_id); if(it == instantiation_cache.end()) { auto timer_pause = fc::make_scoped_exit([&](){ trx_context....


1

This got me as well, it's related to the new WTMSIG_BLOCK_SIGNATURES in eosio 2.0 and the requirement to pre-activate the new eosio chain. There is a pull request which includes a simplified version of the eosio.bios contract called eosio.boot which once deployed gives you the ability to pre-activate and then activate the necessary features. Details can be ...


1

There is no way to calculate this from within the action. The available CPU time is too complicated and depends on too many external variables. The actions are suposed to be determinsitic and repetable exactly as they ran in the first time so no external info which is dynamic is allowed in the dapp action code. You should optimize and test and design your ...


Only top voted, non community-wiki answers of a minimum length are eligible