On Fri, May 11, 2012 at 04:52:33PM +0100, Dave Mitchell wrote:
> On Fri, May 11, 2012 at 04:22:18PM +0100, Tim Bunce wrote:
> > Dave, I'd be grateful if you could take a look at this since it
> > seems to involve our recent changes and standard perl modules.
>
> I can
On Fri, May 11, 2012 at 04:22:18PM +0100, Tim Bunce wrote:
> Dave, I'd be grateful if you could take a look at this since it
> seems to involve our recent changes and standard perl modules.
I can reproduce. Am looking into it.
--
That he said that that that that is is is debatable, is debatable.
> Note that this and the just-submitted DBIS patch represent the end of
> my work on improving performance on DBI, (not counting any remedial work
> that may be required).
PS - here are some final timings, comparing my
'while ($sth->fetch()) {$c++}'
test loop (with unchanged DBD-mysql-4.020),
On Mon, Apr 16, 2012 at 03:12:07PM +0100, Tim Bunce wrote:
> On Fri, Feb 24, 2012 at 05:18:14PM +0000, Dave Mitchell wrote:
> > (I confess I haven't looked closely at this yet, but...)
>
> [And I confess I forgot about this message - sorry for the delay.]
>
> &g
On Fri, Mar 02, 2012 at 05:04:29PM +, Dave Mitchell wrote:
> On Fri, Mar 02, 2012 at 03:23:30PM +0000, Dave Mitchell wrote:
> > I'd be happy in principle, although some guidance would be welcome
>
> Also in particular, what needs to continue happening across an API
> ch
On Fri, Mar 02, 2012 at 03:23:30PM +, Dave Mitchell wrote:
> I'd be happy in principle, although some guidance would be welcome
Also in particular, what needs to continue happening across an API
change? Is it just that a driver, compiled and installed against an old
DBI, must continue
On Fri, Mar 02, 2012 at 03:11:17PM +, Tim Bunce wrote:
> On Fri, Feb 10, 2012 at 03:27:24PM +0000, Dave Mitchell wrote:
> I'm concerned that changing the API, and thus forcing all compiled
> drivers to be recompiled at the same time the DBI is installed,
> isn't worth t
(I confess I haven't looked closely at this yet, but...)
I seems that the imp_xxh_t structure is stored in the PVX of an SV
pointed to by mg_obj. Is there any reason why it can't be just directly
malloced and pointed to from mg_ptr instead?
--
The warp engines start playing up a bit, but seem t
The 8 attached patches (to be applied in sequence) all provide tweaks,
cleanup, or otherwise attempt to make DBI_dispatch go a little bit faster.
This speedups are all relatively minor, and my timings show the
cumulative speedup for my standard fetch() test loop is somewhere between
0% and 9% based
On Wed, Feb 22, 2012 at 02:50:46PM +, Martin J. Evans wrote:
> On 22/02/12 11:09, Dave Mitchell wrote:
> It didn't:
> It is possible the following is the relevant code after preprocessing:
Hi, it turns out that it's a different section of code, but looking at the
right bi
On Wed, Feb 22, 2012 at 10:04:45AM +, Martin J. Evans wrote:
> DBI.xs(4291) : error C2275: 'SV' : illegal use of this type as an expression
> C:\Perl\lib\CORE\perl.h(2243) : see declaration of 'SV'
...
> Lines 4291 and 4292 are:
> MY_CXT_INIT;
> (void)MY_CXT; /* avoid 'unused va
On Fri, Feb 10, 2012 at 10:03:06AM -0800, Jan Dubois wrote:
> On Fri, 10 Feb 2012, Tim Bunce wrote:
> > On Fri, Feb 10, 2012 at 03:27:24PM +0000, Dave Mitchell wrote:
> > >
> > > If anyone knows of a more elegant way to make a function from DBI.xs
> > > availab
On Mon, Feb 13, 2012 at 03:42:21PM +, Dave Mitchell wrote:
> On Mon, Feb 13, 2012 at 01:43:00PM +, Martin J. Evans wrote:
> > It seems to come from the following in DBI.xs:
> >
> > #ifdef HvMROMETA /*introduced in 5.9.5 */
> > + HvMROMETA(s
On Mon, Feb 13, 2012 at 01:43:00PM +, Martin J. Evans wrote:
> It seems to come from the following in DBI.xs:
>
> #ifdef HvMROMETA /*introduced in 5.9.5 */
> + HvMROMETA(stash)->cache_gen
> #endif
It turns out that the function mro_meta_init wasn't exported in 5.10.0,
only in
On Thu, Jan 26, 2012 at 12:26:44PM +, Tim Bunce wrote:
> On Wed, Jan 25, 2012 at 05:37:13PM -0800, Jan Dubois wrote:
> > On Wed, 25 Jan 2012, Tim Bunce wrote:
> > > On Wed, Jan 25, 2012 at 04:14:07PM +0000, Dave Mitchell wrote:
> > >
> > > > PS - I&
On Thu, Feb 09, 2012 at 11:10:17PM +0100, demerphq wrote:
> Well perls fork() relies on threaded perl so it could very easily be
> Dave's patch. Dave do you have access to a win32 build environment?
I'm afraid not.
--
All wight. I will give you one more chance. This time, I want to hear
no Wube
On Wed, Feb 08, 2012 at 10:58:37AM +, Tim Bunce wrote:
> > PS - I'm currently working on bringing PERINTERP and DBIS into the
> > Brave New World of MY_CXT.
>
> Wonderful!
>
> I presume that'll cause an API change that'll require compiled drivers
> to be recompiled (ie. we'd bump DBISTATE_VER
On Tue, Feb 07, 2012 at 10:54:12PM +, Tim Bunce wrote:
> > -if (!imp_msv) {
> > +if (!imp_msv || !GvCV(imp_msv)) {
>
> What's the GvCV test for?
One of the more vicious tests in t/31methcache.t does
local $DBD::Sponge::st::{fetch};
which causes gv_fetchmeth(...,'fetch')
On Mon, Jan 30, 2012 at 10:56:37PM +, Tim Bunce wrote:
> On Mon, Jan 30, 2012 at 12:48:32PM +0000, Dave Mitchell wrote:
> > So I'm tempted to stick with the magic approach. I could optimise
> > it to assume the cache magic is always the first one (and if not, take a
> &g
On Sun, Jan 29, 2012 at 10:06:58PM +, Tim Bunce wrote:
> On Sun, Jan 29, 2012 at 06:12:50PM +0000, Dave Mitchell wrote:
> > The code itself (see diff below) just attaches some magic to the outer CV
> > that caches the GV of the corresponding inner method.
>
> Any rea
On Wed, Jan 25, 2012 at 04:14:07PM +, Dave Mitchell wrote:
> then the CPU usage of the while loop broke down as follows:
>
> 7.0% overhead of loop, i.e. while() {$c++}
>19.2% handle the outer method call, i.e. $sth->fetch()
> of which hal
On Fri, Jan 27, 2012 at 02:53:47PM +, Tim Bunce wrote:
> On Wed, Jan 25, 2012 at 08:17:27PM +, Tim Bunce wrote:
> > On Wed, Jan 25, 2012 at 04:14:07PM +0000, Dave Mitchell wrote:
> > > Just out of curiosity, why can't threaded perls use it?
> >
> > To be
On Tue, Jan 24, 2012 at 08:42:28PM +, Tim Bunce wrote:
> On Mon, Jan 23, 2012 at 12:51:12AM +0000, Dave Mitchell wrote:
> > In the particular case I've been investigating, the method lookup in
> > XS_DBI_dispatch() contributed a measurable part of the total loop time;
>
[ disclaimer: I am being funded to do this work ]
I've been looking into bottlenecks in a tight fetch loop with millions of
rows, e.g.
$sth->bind_columns(...);
while ($sth->fetch) {
# do a small amount of work
}
In the particular case I've been investigating, the method looku
On Mon, Dec 29, 2008 at 09:20:23PM -0500, Matthew Persico wrote:
> On Mon, Dec 29, 2008 at 2:35 AM, Rafael Garcia-Suarez
> wrote:
> > 2008/12/29 Matthew Persico :
> >> Perl - 5.10.0
> >> $ ls -la ~/foo
> >> -r-xr-xr-x 1 persicom develop0 Dec 28 21:15 /home/persicom/foo
> >>
> >> Perl
25 matches
Mail list logo