Bulk Operation - Action: is there a maximum number of records to select for optimal performance?

[Deanobeano2]

Hi

I've just tested the Bulk Operation for an Action on 7 records which worked as anticipated so I then decided to jump in the deep end and perform the bulk operation on the remaining 570 or so records. Currently, the process is absolutely crawling and so I'd like to know if there is maybe a maximum number of records to select for optimal performance e.g. 100 records.

Kind regards
Dean

[amandajane-mo]

Hi Dean, We do ours in batches of 100, never had any issues with actions completing, just carry on with something else while it’s doing its thing, this was definitely quicker than doing 100s at a time. Maybe try 50 if you want it to run a little faster. Amanda

…

On Sat, 22 Mar 2025 at 22:06, Deanobeano2 ***@***.***> wrote: Hi I've just tested the Bulk Operation for an Action on 7 records which worked as anticipated so I then decided to jump in the deep end and perform the bulk operation on the remaining 570 or so records. Currently, the process is absolutely crawling and so I'd like to know if there is maybe a maximum number of records to select for optimal performance e.g. 100 records. Kind regards Dean — Reply to this email directly, view it on GitHub <#472>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATAWKKZQ5ML62WPFEKLPXNL2VXNFXAVCNFSM6AAAAABZSJXHICVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYGEYTQMBSGU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Deanobeano2]

Hi Amanda

The process "died" after writing about only 130 records.

My batches of 50 records at a time to complete the remaining records all went well as expected. I'll try batches of 100 records next week.

Kind regards
Dean

[cortexrd]

Hi Dean,

I've also noticed that above 100 records, Knack (+KTL) struggle a lot with even simple features. I think it has to do with the intensive memory consumption due to jQuery among other things. I didn't spend too much time trying to understand and do some profiling, analysis, etc.

What you can try is to use smaller grids, with as little columns as possible to see if it helps.

Otherwise, go for the obvious: keep the batches smaller at 100 records at a time.

The good news is: Knack's Next Gen app won't use jQuery anymore. This means there are chances we'll see some performance improvements.

We'll see.

Norm