incubator-lucy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marvin Humphrey <mar...@rectangular.com>
Subject Re: [lucy-user] Perl modules used on different machines (very slow search on one, but not other)
Date Tue, 27 Sep 2011 21:43:22 GMT
On Tue, Sep 27, 2011 at 02:24:04PM +0200, goran kent wrote:
>  18.3   0.306  0.512   5162   0.0001 0.0001  Text::Balanced::_match_variable
>  13.9   0.233  0.275   4280   0.0001 0.0001  Text::Balanced::_match_quotelike
>  11.4   0.191  0.962     20   0.0095 0.0481  Switch::filter_blocks
>  6.52   0.109  0.109  10596   0.0000 0.0000  Text::Balanced::_failmsg
>  6.40   0.107  0.307   2408   0.0000 0.0001  Text::Balanced::_match_codeblock
>  4.19   0.070  1.668     16   0.0044 0.1043  main::BEGIN

> It looks like it's got something to do with Lucy deciding to use the
> Perl module Text::* at configure time, but I may be wrong.

Text::Balanced and Switch are not dependencies of Lucy, so the reasons they
are being loaded conditionally lie elsewhere.
 
> What should I look for to get an idea why this is happening?

Probably just grep for those class names in your code base to start with.  If
that doesn't reveal the culprit, I seem to recall that there are techniques
for finding out exactly when a module gets loaded, but I forget what they are.
Maybe try perlmonks.org if you're still stumped.
 
> On slow machine, the following fails:
> t/core/051-fs_file_handle.t .......... Failed 42/46 subtests
> t/core/103-fs_folder.t ............... 1/108 Can't clean up directory _fstest
> 	S_tear_down at
> /home/gk/projects/lucy/lucy/perl/../core/Lucy/Test/Store/TestFSFolder.c
> line 67
> 	at t/core/103-fs_folder.t line 20
> t/core/103-fs_folder.t ............... Dubious, test returned 39
> (wstat 9984, 0x2700)
> Failed 106/108 subtests

The TestFSFolder test file fails intermittently on certain systems (I've seen
it most often with MSVC), and I've never figured out why; then when it fails,
it does not clean up after itself properly.  Delete that _fstest dir and the
test may well pass afterwards.  If it continues to fail, that's great news --
you can help me debug it. :)

Cheers,
 
Marvin Humphrey


Mime
View raw message