Home/ Questions/Q 3985574
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T05:54:24+00:00

I am developing an application with Fluent nHibernat/nHibernate 3/Sqlite. I have run into a

  • 0

I am developing an application with Fluent nHibernat/nHibernate 3/Sqlite. I have run into a very specific problem for which I need help with.

I have a product database and a batch database. Products are around 100k but batches run in around 11 million+ mark as of now. When provided with a product, I need to fill a Combobox with batches. As I do not want to load all the batches at once because of memory constraints, I am loading them, when the product is provided, directly from the database. But the problem is that sqlite (or maybe the combination of sqlite & nh) for this, is a little slow. It normally takes around 3+ seconds to retrieve the batches for a particular product. Although it might not seem like a slow scenario, I want to know that can I improve this time? I need sub second results to make order entry a smooth experience.

The details:

  • New products and batches are imported periodically (bi-monthly).
  • Nothing in the already persisted products or batchs ever changes (No Update).
  • Storing products is not an issue. Batches are the main culprit.
  • Product Ids are long
  • Batch Ids are string
  • Batches contain 3 fields, rate, mrp (both decimal) & expiry (DateTime).

The requirements:

  • The data has to be stored in a file based solution. I cannot use a client-server approach.
  • Storage time is not important. Search & retrieval time is.
  • I am open to storing the batch database using any other persistence model.
  • I am open to using anything like Lucene, or a nosql database (like redis), or a oodb, provided they are based on single storage file implementation.

Please suggest what I can use for fast object retrieval.

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You need to profile or narrow down to find out where those 3+ seconds are.

    Is it the database fetching?
    Try running the same queries in Sqlite browser. Does the queries take 3+ seconds there too? Then you might need to do something with the database, like adding some good indexes.

    Is it the filling of the combobox?
    What if you only fill the first value in the combobox and throw away the others? Does that speed up the performance? Then you might try BeginUpdate and EndUpdate.

    Are the 3+ seconds else where? If so, find out where.

    • 0