Donald Allen <donaldcal...@gmail.com> writes:
>> I think true measurements will be the only way to find out what causes delays
>> where.
>
> Of course. I spent a big chunk of my career doing performance analysis
> on various bits of complicated software and learned very young (the
> hard way) that if you think you know how your software behaves and
> where the time is going, you are probably wrong. Measurement, done
> correctly, is the only way to get to the truth reliably. I sometimes
> had to insist on measurement by people who worked for me who were as
> cocky (and wrong) as I was when I was young :-)
>
> But until the measurements are done, there's no harm in doing some
> educated guessing, so long as the guessing doesn't replace the
> measuring. If you are frequently right, it can help you set your
> measurement priorities. If you are frequently wrong, it reminds you
> that you aren't too good at modeling the behavior of software in your
> head.
For what it's worth, the old Postgres backend was dog slow too.
I certainly encourage you to perform profiling to determine where our
bottlenecks are.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warl...@mit.edu PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
