You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Jérôme Etévé <je...@gmail.com> on 2009/10/23 15:26:58 UTC
QTime always a multiple of 50ms ?
Hi all,
I'm using Solr trunk from 2009-10-12 and I noticed that the QTime
result is always a multiple of roughly 50ms, regardless of the used
handler.
For instance, for the update handler, I get :
INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=0
INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=104
INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=52
...
Is this a known issue ?
Cheers!
J.
--
Jerome Eteve.
http://www.eteve.net
jerome@eteve.net
Re: QTime always a multiple of 50ms ?
Posted by Lance Norskog <go...@gmail.com>.
This is different for each model of computer. It has to do with
exactly what chips are used.
On Fri, Oct 23, 2009 at 10:42 AM, Jérôme Etévé <je...@gmail.com> wrote:
> 2009/10/23 Andrzej Bialecki <ab...@getopt.org>:
>> Jérôme Etévé wrote:
>>>
>>> Hi all,
>>>
>>> I'm using Solr trunk from 2009-10-12 and I noticed that the QTime
>>> result is always a multiple of roughly 50ms, regardless of the used
>>> handler.
>>>
>>> For instance, for the update handler, I get :
>>>
>>> INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=0
>>> INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=104
>>> INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=52
>>> ...
>>>
>>> Is this a known issue ?
>>
>> It may be an issue with System.currentTimeMillis() resolution on some
>> platforms (e.g. Windows)?
>
> I don't know, I'm using linux 2.6.22 and a jvm 1.6.0
>
>
> --
> Jerome Eteve.
> http://www.eteve.net
> jerome@eteve.net
>
--
Lance Norskog
goksron@gmail.com
Re: QTime always a multiple of 50ms ?
Posted by Jérôme Etévé <je...@gmail.com>.
2009/10/23 Andrzej Bialecki <ab...@getopt.org>:
> Jérôme Etévé wrote:
>>
>> Hi all,
>>
>> I'm using Solr trunk from 2009-10-12 and I noticed that the QTime
>> result is always a multiple of roughly 50ms, regardless of the used
>> handler.
>>
>> For instance, for the update handler, I get :
>>
>> INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=0
>> INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=104
>> INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=52
>> ...
>>
>> Is this a known issue ?
>
> It may be an issue with System.currentTimeMillis() resolution on some
> platforms (e.g. Windows)?
I don't know, I'm using linux 2.6.22 and a jvm 1.6.0
--
Jerome Eteve.
http://www.eteve.net
jerome@eteve.net
Re: QTime always a multiple of 50ms ?
Posted by Andrzej Bialecki <ab...@getopt.org>.
Jérôme Etévé wrote:
> Hi all,
>
> I'm using Solr trunk from 2009-10-12 and I noticed that the QTime
> result is always a multiple of roughly 50ms, regardless of the used
> handler.
>
> For instance, for the update handler, I get :
>
> INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=0
> INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=104
> INFO: [idx1] webapp=/solr path=/update/ params={} status=0 QTime=52
> ...
>
> Is this a known issue ?
It may be an issue with System.currentTimeMillis() resolution on some
platforms (e.g. Windows)?
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com