Maximum Number of Images?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- ios, swift
- Domain
- mobile, performance
Research direction
Start by reproducing the index update with a large photo library and record where indexing stops, then compare launch and subsequent search times. Inspect the app's indexing and model-loading paths; done means indexing completes without the reported crash and search performance or its limiting behavior is documented.
Written by the indexing model from the issue text.
Description
I have been making heavy use of Queryable and really enjoying it. However, it recently seems to have hit some internal limit on the total number of images it supports. When I update the index it shows progress up to 4,900/total then crashes like it normally does due to the memory leak (usually the memory leak crash is at 10,000-20,000). However, when I restart the app the total number to index is unchanged.
I tried deleting and reinstalling the app in case my index got somehow corrupted. A bit over 200,000 images into my 300,000 image library the same thing started happening again. I thought it was notable that the images being indexed were different for the crash before the reinstall and after. Also, before the reinstall it had indexed about 50,000 more before getting stuck at the 4,900 index crash.
Also, as my library has gotten bigger performance has gotten quite a bit worse. It is currently taking about 70 seconds to launch the app, have the model load and successfully complete the first search. Subsequent searches take about 45 seconds each to complete once I hit search. (I am using an iPhone 14 Pro Max).
I assume this is due to my picture library size but if speed up is possible I would really appreciate it.
- Dominant language
- Swift
- Stars
- 3k
- Forks
- 448
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mazzzystar/Queryable
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
mazzzystar/Queryable#53 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
mazzzystar/Queryable#48 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
mazzzystar/Queryable#42 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mazzzystar/Queryable#41 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
mazzzystar/Queryable#40 ·
All issues in mazzzystar/Queryable
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
type: docs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
googleapis/google-cloud-swift#971 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bitcoindevkit/bdk-ffi#1125 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mozilla-mobile/firefox-ios#35743 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
manaflow-ai/cmux#13417 ·