nostr:npub19lt4284mghqxekzm6n5njxurnxrxhqhrva2leusdsuu5ja5jeycq66qfjk If you want a rough and ready figure you can call microtime before and after and compare the results, likewise memory_get_usage. They aren't great but they will probably tell you if one function is taking 10x as long as another.

If they're not enough then really Xdebug + an analyser such as KCacheGrind are the way to go.

https://3v4l.org/ allows you to run code online but I don't think it would help with profiling.

Reply to this note

Please Login to reply.

Discussion

nostr:npub19lt4284mghqxekzm6n5njxurnxrxhqhrva2leusdsuu5ja5jeycq66qfjk In my experience though, the things that really kill performance are function calls and database queries, especially if performed in loops. There's not usually a huge gain from tweaking other parts of the code.