You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
forp_stats() this should give information about the dump. Like how many functions calls are in it. The total script execution time stuff like that if its possiable just so you dont have to dump to find out and dumps can make you run out of memory also to be able to page the dump output. So if you want to dump 1000 function calls at a time instead of dumping all 100k function calls (great for frameworks)
The text was updated successfully, but these errors were encountered:
I think your request makes sense but it's contrary at the main idea of forp : the module was initialy designed just to store and send execution stack data - the UI and process of this data is an independ project
That means the forp module should be the most abstracted possible with the data processing
By the way, it's already implemented on the Javascript GUI, and you can also aggregate stats on with forp_dump in a custom php script, BUT I'm agree with you that both could overkill the memory.
If the stack is big (lets say more than 100 000 instructions) the memory usage on the server will be too big for generating the forp_dump, and even if it's passing, the browser will freeze.
So I'm planning to try an implementation of your request directly in the forp module that will return an array (with stats like the forp UI) - forp_stats that will return an array of aggregated data.
I think that a few things could be added.
forp_stats() this should give information about the dump. Like how many functions calls are in it. The total script execution time stuff like that if its possiable just so you dont have to dump to find out and dumps can make you run out of memory also to be able to page the dump output. So if you want to dump 1000 function calls at a time instead of dumping all 100k function calls (great for frameworks)
The text was updated successfully, but these errors were encountered: