Andrea, Just tried it with latest build of Brooklyn (both br and dist). I get the following timings: real 0m0.034s user 0m0.006s sys 0m0.011s
So seems it's context sensitive. Doing a wireshark capture and comparing the output for curl and br could help in pinpointing where the problem is. Svet. > On 1.12.2016 г., at 14:06, Alex Heneveld <alex.henev...@cloudsoftcorp.com> > wrote: > > the CLI has felt a little bit slow at times. i had chalked it up to bad > networking and it hasn't been a big issue. but if there are some easy > optimisations which would noticeable improve user experience -- which > andrea's timing data makes me think might be possible -- that would be nice! > > --a > > > On 1 December 2016 at 11:19, Geoff Macartney < > geoff.macart...@cloudsoftcorp.com> wrote: > >> hi Andrea, >> >> it's not something I'd noticed myself. `br` would be a bit slower than >> curl but it shouldn't be dramatic. I'll look into it, but it would be >> certainly good to hear others' experiences here? >> >> cheers >> Geoff >> >> >> >> On Thu, 1 Dec 2016 at 11:04 Andrea Turli <andrea.tu...@cloudsoftcorp.com> >> wrote: >> >>> Hi team, >>> >>> I'm comparing br cli performance vs plain curl commands and this is some >> of >>> the surprising results I'm seeing: >>> >>> $ time br app myApp entity myEntity sensor > /dev/null >>> >>> real 0m3.833s >>> user 0m0.008s >>> sys 0m0.010s >>> >>> and >>> >>> $ br login http://brooklyn:8081 user password >>> $ time curl -s -u user:password -X GET --header "Accept: >> application/json" >>> " >>> >>> http://brookyln:8081/v1/applications/myApp/entities/ >> myEntity/sensors/current-state >>> " >>>> /dev/null >>> >>> real 0m0.400s >>> user 0m0.005s >>> sys 0m0.004s >>> >>> I’d expect some slow down but not that much. >>> >>> Is it something others are experiencing as well? >>> >>> Best, >>> Andrea >>> >>
