Using modifyTimeStamp in queries

We have an application that needs to query for and return thousands of entries with modifyTimeStamp greater than a given time. This is turning out to be too slow for this app and so I'm wondering if there's any way to speed this up other than throwing more CPU at it.

Tim Darby

[William Brown]

> On 1 Nov 2024, at 08:51, tdarby--- via 389-users  wrote:
>
> We have an application that needs to query for and return thousands of entries with modifyTimeStamp greater than a given time. This is turning out to be too slow for this app and so I'm wondering if there's any way to speed this up other than throwing more CPU at it.

Is modifyTimestamp indexed?

Have you raised your idlscanlistlimit to 999999999?

Sounds like you have a full table scan going on. The above two changes will fix it.

[EXT] Re: Using modifyTimeStamp in queries

[Darby, Tim - (tdarby)]

Thanks! Which index should I put on modifyTimestamp?

Tim Darby
________________________________
From: William Brown via 389-users 
Sent: Thursday, October 31, 2024 16:52
To: [e-mail] 
Cc: Darby, Tim - (tdarby) ; William Brown 
Subject: [EXT] [389-users] Re: Using modifyTimeStamp in queries

External Email

________________________________

On 1 Nov 2024, at 08:51, tdarby--- via 389-users  wrote:

We have an application that needs to query for and return thousands of entries with modifyTimeStamp greater than a given time. This is turning out to be too slow for this app and so I'm wondering if there's any way to speed this up other than throwing more CPU at it.

Is modifyTimestamp indexed?

Have you raised your idlscanlistlimit to 999999999?

Sounds like you have a full table scan going on. The above two changes will fix it.

--
Sincerely,

William Brown

Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia

[EXT] Re: Using modifyTimeStamp in queries

[William Brown]

Equality should be the index you need. It implies ordering depending on the type.
> On 2 Nov 2024, at 03:26, Darby, Tim - (tdarby) via 389-users  wrote:
>
> Thanks! Which index should I put on modifyTimestamp?
>
> Tim DarbyFrom: William Brown via 389-users 
> Sent: Thursday, October 31, 2024 16:52
> To: [e-mail] 
> Cc: Darby, Tim - (tdarby) ; William Brown 
> Subject: [EXT] [389-users] Re: Using modifyTimeStamp in queries
>  External Email
> > On 1 Nov 2024, at 08:51, tdarby--- via 389-users  wrote:
> >
> > We have an application that needs to query for and return thousands of entries with modifyTimeStamp greater than a given time. This is turning out to be too slow for this app and so I'm wondering if there's any way to speed this up other than throwing more CPU at it.
>
> Is modifyTimestamp indexed?
>
> Have you raised your idlscanlistlimit to 999999999?
>
> Sounds like you have a full table scan going on. The above two changes will fix it.
>
> -- 
> Sincerely,
>
> William Brown
>
> Senior Software Engineer,
> Identity and Access Management
> SUSE Labs, Australia
>
> -- 
> _______________________________________________
> 389-users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]....
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue