What do you mean about the images and files, specifically? If embedding images within an org file, it is super easy, just do ‘[[file://image/path.jpg]]’ and run M-x org-toggle-inline-images (i think that’s the command).
My org files (all of which reside in my agenda directory, ~/org) are divided primarily into archives.org (i keep a datetree log here), wiki.org (bookmarks, notes etc), and tasks.org. With sparse trees, narrowing to subtree etc I tend to keep big monolithic files and just filter for the view I want, though many seem to prefer smaller ones (i find it harder to sync more files and directories though, and I’m unsure of the advantages more files provide).
So you have all images of all org docs in one folder? Or one folder per org file? The first would be better for refiling across files, the latter better for portability of the org files.
How many lines does your bigger org than have? My main one has 1.5k. My archive (just a year old maybe) has 15k and many org functions become quite slow, even freezing emacs sometimes.
>So you have all images of all org docs in one folder?
I'm not sure what you by 'all images of all org docs', but I keep most my org-related images in one file (my archive.org, where I store most of them in an ongoing datetree under a relevant header). Most of the photos I keep in org-mode revolve around logging though - things like bread, beer, garden plants, etc - but I also have some images kept in my notes sections. And yeah, all of my org files are in ~/org. I used to use many files and directories, but it made it annoying for syncing across devices, and having shorter paths is nice anyway.
>How many lines does your bigger org than have? My main one has 1.5k. My archive (just a year old maybe) has 15k and many org functions become quite slow, even freezing emacs sometimes.
My largest one is around 1.5k, after some heavy pruning last week. I respect your 15k archive! I only recently started taking my archiving seriously, and I've really enjoyed it so far. Keeping ALL of my logs (photography, work outs, diet, bread making, etc) under one datetree has brought a lot of Zen to my workflow. Unfortunate though that you experience performance issues at that size. Perhaps looking into `M-x profiler-report` could give you some leads? This will at least tell you what functions are using the most CPU or Mem, and you can potentially adjust accordingly from there. It is likely some package(s) using too many resources.
and what are the limits to keeping everything in one file? theoretically i see no downside to it.