It would be good to know which object is eating up the CPU. Sometimes its impossible to figure out exactly which object is eating up CPU. Quite often, there is a particular object that will eat every signle bit of CPU, and its impossible to track it down… In M4L this sometimes happens after 30 minutes of using a patch, making it even more difficult to understand where and why it is happening. Just a simple % of each object and the CPU it is using would be good.
i know .
-- Pasted Max Patch, click to expand. --Copy all of the following text. Then, in Max, select New From Clipboard.----------begin_max5_patcher---------- 626.3oc0WssbaCBD8YmYx+.COq3AzEjceqeGc5jAIQRHUFzfPotIS+2KWjrc ZssvMJpou.lkE1yd7dA8x0Ws.VH2xZgfOA9BXwhWLRV3jYkrXPvB3F51xZZq SQ3c0RQ2FXT+d2IE5V9yL6d33knCkKnabxgeVwo06Nh43xNcMS6tv3Aw7Jmt xhGuIAuS4Fpt7At39aUrRsGoqvFy.hSrVCjgbKLifuNbF+sq+QCye.KloZXD .VPE2C2qnAIbw.Pv6Mox.bMScKSPKpcWBxs2Ou9J6rYJJX9pnSqkhS373i47 ny473TmaGu1474Cimw4OqO+W6VB12MfcGR0rsN.B0JpnUQ0b4ngHkxZop2qr 9AZYRRdbVl8WD7ZBZUjci8PO3XpiQq37wiovqSsSDb.wTmhRimbJs6YN.iPn oKmK4X7S543mXWZFF4y4HAvOtvtn8ybgd5orKN4BiF2K6ysVMLN64VyQI17w 4gDrOoHE+AuD6oRbtwTHY5XwiENQBHZJmbor3rUYoroqrVV9s2WRJKf9Y8Ud 8MzdKjD9+TRJjpueb4HMn.PPfh24VTAvQ92CFV11gslhtrh4d0f0bwe79YG1 ra7aDYqrSUNX5gdQfCvWEqUyE1mNINTqzWq0C7pJlSgcjZEu0VDsZjpngCrz f.17iq7PvUx+.fYrHdT9Je1wUBZZ9ibCupQZxR5C0wY3klWoiSH8OWZXwAVZ h8DRHNx7SvYg.KxqiNlo3w3wfU1ryVogxVye16nv5sUEtucAso4Ilps+l8Hx zf8Q+mASh7q4B+Z+yDfJ1S7gizqBUY59oMs95T9NoaIoPyNNCZF9EjZDsiJ -----------end_max5_patcher-----------
sometimes it helps to find out how long it take for an operation to finish , i dont know any better way .
if you are using preset interpolation , or automating parameters that are in relation with pattrstorage , you may see higher cpu utilization .
EDIT : updated
Cool! This will help with the flow in certain processes. What about continuous processes? For instance if I have a counter driving a dial, the process never ends, so Im wondering how I can detect cpuclock time? Ive just put a [speedlim 50] on there for the time being, but id love to know why this is happening. Wish I knew more about these objects and how they can be used to optimise :)
you cant get precise results here as object that measure "stuff" also are doing their job with CPU at time .and often from time to time the result might vary , you can see also that UZI results differently (it bangs fast like crazy) , but the result is somehow compromised or optimized , not sure (or its spread over cpu cores ? really not sure ,as im seeing faster times than simple bangs).
you can bang your "buddies" as shown in the patcher through the middle outlet of "our" trigger .
-- Pasted Max Patch, click to expand. --Copy all of the following text. Then, in Max, select New From Clipboard.----------begin_max5_patcher---------- 705.3oc0WssbaBCD8YmYx+.COS7Hw0j9V+N5jwiLnjnDrjGgv0IY5+dWjPX6 TvnjRHs1iEHsKnydzQ6J+5kWrvesXOsx26ad+vawhWgQVnGqYjE1AV3ugrOu jToczujsitrfQJ8CZMuiH4jMzArxq2HpUkTk9wCsCyJz9KV+3UQocNuknxef wuekjlqL35Z7RTfWXXTyk3Xca1Rj2s1mw71UOukZd.e+.O+6JED3Eb6Qnfws f.eX5j.vUT4JJmrtjdhwJxNZwJhRIYqqUzC2U0ROV9ogAJqoh6ri2Y33YnTv ueXZ5DWqdPHUN5qMtw8YbCrxoMh.ZqG60blpR8rIvQsN7qKuvbm8l1qvk.mU Ib5Ogk1t0UEcud4zOWTygY1CAXpy5cBtph8hINB6fpd7NZ36xgUUw8opRFWU guQqmxxzRLzYUULtpQXY+0zc.4UxGl0.0kRvGHHw8EjnyEj33PcfcSSaRls8 LA4ZB+9A20L4hg5WXfL.9LcJgndHIb74HolkcPIfzTUZjCJAMIEb35YjBgym T.iFOJaUBWaamck.jVFdSS2xcekSxFmGhvls+wXGVtMkRBFgRNWIEzjuy4JO zxoiE6SNk5fZJK88xhS91jAqyrsNuTj+zmKIk3P121ZLIY+sjD9+TRxkru+6 xQJu0Me+jqP4.Ekfbey1aqP8dRlabCN0I+O9mAZv0X3MDYknVlama6Yu7NBf EzJEiSTLnh1QdkdpWOvJJnZG5X0BVUSRzhQxh5Lv.h1COJtRlebgbgvZNHyb CrXm.1WxB4nvJ9KAVgiAq4WdEgllUwMrhsB33tsIFvI3kIvFpnz1CWZ6bzLM wQRpKAR1rSvNkuK8zjOy.rhcEVeb1psbAY61cTYU6a1fHn.6iBYS+z.SeF2z 2bLAeIcGy9HstPjP4OET6qVZJktOM1GrnmPn42vpDgxX -----------end_max5_patcher-----------
as for optimization . the less on the road the faster / lighter for CPU .
a counter will always need the same processing power, for every value it outputs.
Forums > MaxMSP