> On Aug 18, 2016, at 3:33 AM, Michael Schuster <[email protected] > <mailto:[email protected]>> wrote: > having "grown up", as it were, on Solaris, my gut reaction to "performance" > issues is "use dtrace", which, happily, OS X has (to some extent). > > I'm afraid I can't supply anything specific myself here (tempted as I am), > but I'll point to James C McPherson's post as a starter: > https://www.darktable.org/2012/05/darktable-and-solaris-it-just-workstm-and-there-are-some-nifty-benefits-too/ > > <https://www.darktable.org/2012/05/darktable-and-solaris-it-just-workstm-and-there-are-some-nifty-benefits-too/> > (though latency from Germany is truly awful, YMMV, be patient :-).
Unfortunately my dev days are far far behind me. :) I’m definitely one of those “if I don’t use it, I lose it” types and rusty doesn’t even begin to describe my development skills these days. I moved into sys admin and telecom work a number of years ago after doing physics simulations back in the early CUDA days along with some hardware interfacing work. So I’m not sure I could provide much in the way of useful info there. > (if you're on a recent release of OS X, you'll probably need something like > this first: http://internals.exposed/blog/dtrace-vs-sip.html > <http://internals.exposed/blog/dtrace-vs-sip.html>) Thanks for the info there. I had to kext signing in SIP already for some older scanner drivers. I’ve heard Homebrew users were having problems with SIP too. Although being an old FreeBSD person myself I stuck with MacPorts and SIP doesn’t bother it. Thanks again! Leander ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
