Jump to content

Astara

Members
  • Posts

    5
  • Joined

  • Last visited

  1. Not much to show in the way of a screen shot since Designer no longer starts at all and just crashes. I could post trace files -- but having a similar bug on Photo, I note there was no interest in the trace or coredump files in the Designer subdir in my app-profile. Weird how both of them worked in previous version, but now both of them crash on startup. Maybe there is code common to both that is causing the problem? What are operations that Photo & Designer share?
  2. I noted in reviewing a trace @ startup due to another problem, that in reading in the fonts, 1) many or most were read in more than once, some more than 2 times. I don't know exactly why this is the case, I thought I knew, and thought man were links to others with one being a short name and another being a long name, but in examining the files more closely, out of 11082 files in the win font dir, 10353 were unique (729 files were links to another file). One source of many fonts -- many fonts come in different styles, as well as supporting different locales (most of those from pre unicode days). Windows will group those together which brings the total down to about 3900. 2) a file-system stat is done when each font is read in -- the fonts are on the same filesystem -- it only needs to be read once and the information could be cached. 3) the delay gets really bad when you start more than one serif/affinity at the same time (like designer and photo). 4) Isn't it possible to cache the font information in a more easily read format and update the cache if there are any new fonts or changes that have a more recent modification time than those in the cache? If all the font information was in 1 or a few large files, this would allow reading in all font information in very few I/O operations with the limiting factor being the storage device. 5) all fonts are read in sequentially. Even though reading the fonts is a cpu-bound activity, multiple CPUs idle while the fonts are processed one at a time. The highest I/O rate was 2MB/s on an SSD easily capable of over 400MB/s. Since font-processing time is heavily cpu bound, using multiple cores could really help. Combine parallel processing with doing it in background and the possibility of using a cached copy when fonts are unchanged, the potential for speedup is large.
  3. I don't seem to be able to get Photo or Designer to start after switching to 1.9. I tried to look at the prob -- it seems they crash right after scanning the fonts, but unable to determine why. I'll attach a procmon trace in xml format. The 257MB trace shrank to 6.7M in 7z format. Running Win7SP1x64 on an 8-core (Hyper threading disabled), 96G RAM, w/6-10GB GPU mem on a GeForce RTX 2080 Ti. I haven't used either product extensively since the long time to startup made me lose interest in doing anything. I keep hoping that someone will take the font performance issue seriously, such that it is eliminated, since the serif apps are the only ones with such a problem on every startup, even though I almost never used the font features in photoshop (not a big part of my workflow). They have gotten better, but I note that many of the fonts are read twice and for some reason the font-reading process does a disk-status call with each font lookup, so it doesn't look like much time has been spent trying to make it efficient or fast, not to mention doing the whole font read-in once and caching it -- then updating the cache only when new fonts have been added. Also besides reading the font resources in a background thread, could also get some serious improvement by splitting up the job across multiple cores and merging the results via shared memory, though even a merge-sort on 'N' result files (N maybe # of cores) would likely give a strong speedup. Of course being the masochist that I am, I'll startup both photo+designer at same time because I don't know them very well and not sure which has which features that I might want to try. But now, doesn't want to startup at all. Any ideas? Especially since both crash now? :-( photo-procmon.7z Designer-CrashReports.7z photo_CrashReports.7z
  4. Um...I'm not using a font program for any thing else to function normally and read fonts in <30 seconds. That's the problem: most programs take less than 15 seconds to read in the font list and they only do it when I want to change the font -- not at program startup. Vim takes about 20 seconds, Windows < 10sec on Win7SP1x64. That Affinity Photo takes over 7 times longer than any other program and does it every time at startup, blocks use of the product. Anything that blocks using the product is a high severity bug. If other programs took that long, I would probably think I had too many font files, but the last time I had programs take that long on my fonts was under Windows XP over 15 years ago. Your attitude toward your customers is unfortunate.
  5. I just timed it -- just starting up Affinity Photo -- almost all the time spent in reading fonts took 2minutes and 30 seconds. I don't know how photoshop managed to come up in less than 20 seconds and still have a font list ready to present, but certainly fonts aren't usually the first thing needed in editing photos. I have a relatively fast machine -- 8 cores (hyperthreading disabled), 96G of 2666Mz memory, all running off a RAID0 of 4 SSD's -- oh, and with a GTX 1080, yet it still took over 2 minutes just to read my fonts (have about 10k font files, Some are variations in a family some _MAY_ even be duplicates, though Windows weeds those out in presenting the fonts. Less useful might be only loading the fonts when one goes to access them -- the least disruptive would be them loading in a separate thread in background. When I was drawing, I tended to work in short spurts, but starting/stopping photoshop often because I might want to do some other memory intensive task and it would take (configurable) about 70G with history states and such. My larger drawings, I worked at around 7000x12000 and wouldshrink them down for sharing , but that allowed me to get finer detail. Anyway, the font stuff prevents me from using affinity much cuz by the time it has loaded the fonts, I'm on to something else. (sigh).... thanks... Astara
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.