Seems reasonable. Your laptop likely being faster than a Pi 4B probably explains why that takes half a minute while the Pi 4B takes 3 minutes.But I've tried on a Windows laptop:
Measure-Command {picotool coprodis PicoMite.dis out.dis}
TotalSeconds : 28.5961003
But, that your 'out.dis' should be the same as the input 'PicoMite.dis', as it is for me, means 'picotool coprodis' is taking half a minute to 'do nothing', half a minute to process input to output with no changes being made.
When I run my own Python code utility to do the same as 'picotool coprodis', which also produces the same output as that does ...
Code:
pi@Pi4B:/tmp $ time coprodis PicoMite.dis z.disreal 0m0.512suser 0m0.444ssys 0m0.069sCode:
pi@Pi4B:/tmp $ ls -l *.dis-rw-r--r-- 1 pi pi 11368339 Feb 16 18:20 PicoMite.dis-rw-r--r-- 1 pi pi 4176944 Feb 16 18:20 x.dis-rw-r--r-- 1 pi pi 11368339 Feb 16 18:23 y.dis-rw-r--r-- 1 pi pi 11368339 Feb 17 12:29 z.disIf your complaint is that the picotool coprodis option is slow, then open a github issue against picotool with detail of platforms etc.
Statistics: Posted by hippy — Mon Feb 17, 2025 12:45 pm