search for: numcalls

...instr correspond to ? variable jump? 5) fudge factor prefers functions with vector instructions -- why is that? 6) There is one heuristc used in inline-cost computation seems wrong: // Calls usually take a long time, so they make the inlining gain smaller. InlineCost += CalleeFI->Metrics.NumCalls * InlineConstants::CallPenalty; Does it try to block inlining of callees with lots of calls? Note inlining such a function only increase static call counts. Thanks, David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev...

...instructions are an indicator that the function is a hotspot, and should therefore be inlined. > 6) There is one heuristc used in inline-cost computation seems wrong: > >   // Calls usually take a long time, so they make the inlining gain smaller. >   InlineCost += CalleeFI->Metrics.NumCalls * InlineConstants::CallPenalty; > Does it try to block inlining of callees with lots of calls? Note inlining > such a function only increase static call counts. I'm guessing the heuristic is that functions with lots of calls are heavy and spend a lot of time in their callees, so eliminat...

...gt; 5) fudge factor prefers functions with vector instructions -- why is that? > > 6) There is one heuristc used in inline-cost computation seems wrong: > > > // Calls usually take a long time, so they make the inlining gain > smaller. > InlineCost += CalleeFI->Metrics.NumCalls * InlineConstants::CallPenalty; > > Does it try to block inlining of callees with lots of calls? Note > inlining such a function only increase static call counts. > > > Thanks, > > David > > > > _______________________________________________ > LLVM Developers...

...: http://blog.llvm.org/2010/01/address-of-label-and-indirect-branches.html for more details. > 6) There is one heuristc used in inline-cost computation seems wrong: > > // Calls usually take a long time, so they make the inlining gain smaller. > InlineCost += CalleeFI->Metrics.NumCalls * InlineConstants::CallPenalty; > > Does it try to block inlining of callees with lots of calls? Note inlining such a function only increase static call counts. I think that this is a heuristic that Jakob came up with, but I think it's a good one, also discussed elsewhere on the thread....

...s functions with vector instructions -- why is that? >> >> 6) There is one heuristc used in inline-cost computation seems wrong: >> >> >> // Calls usually take a long time, so they make the inlining gain >> smaller. >> InlineCost += CalleeFI->Metrics.NumCalls * InlineConstants::CallPenalty; >> >> Does it try to block inlining of callees with lots of calls? Note >> inlining such a function only increase static call counts. >> >> >> Thanks, >> >> David >> >> >> >> ____________________...

...s-of-label-and-indirect-branches.html > > for more details. > > > 6) There is one heuristc used in inline-cost computation seems wrong: > > > > // Calls usually take a long time, so they make the inlining gain > smaller. > > InlineCost += CalleeFI->Metrics.NumCalls * > InlineConstants::CallPenalty; > > > > Does it try to block inlining of callees with lots of calls? Note > inlining such a function only increase static call counts. > > I think that this is a heuristic that Jakob came up with, but I think it's > a good one, also d...

List users, Using Asterisk in an inbound call center environment has led us to pushing the limits of vertical scaling. In order to treat each caller fairly and to utilize our agents as efficiently as possible, it is desirable to configure each client as a single queue. As far as I know, Asterisk's queues cannot be distributed across servers, so the size of the largest queue we service

...es: 0 vfs.numdirtybuffers: 90 vfs.lodirtybuffers: 909 vfs.hidirtybuffers: 1819 vfs.dirtybufthresh: 1637 vfs.numfreebuffers: 7108 vfs.lofreebuffers: 404 vfs.hifreebuffers: 808 vfs.getnewbufcalls: 598 vfs.getnewbufrestarts: 0 vfs.flushwithdeps: 0 vfs.cache.numneg: 30 vfs.cache.numcache: 483 vfs.cache.numcalls: 13298 vfs.cache.dothits: 93 vfs.cache.dotdothits: 18 vfs.cache.numchecks: 12063 vfs.cache.nummiss: 1096 vfs.cache.nummisszap: 33 vfs.cache.numposzaps: 23 vfs.cache.numposhits: 11003 vfs.cache.numnegzaps: 10 vfs.cache.numneghits: 1022 vfs.cache.nchstats: 11003 1022 33 0 1129 0 14 79 vfs.cache.numfu...