Can AD handle Files with _many_ Artboards?

[farbenfeuer]

As the title says: I started with the idea to set up just one file for print and one for web for each of my clients. So that would mean i have all the different projects as artboards within one .afdesign file.

Now i'm not so sure if this is intended, or handled well by AD? I guess i would need a quick feedback from a dev, if i should split them back up or if AD can easily handle files with up to 30, 40 or more artboards?

 

I thought this way i could make better use of the document restricted symbols (you know, cause you can use symbols only within the same documents). In the meantime we got assets though and i'm wondering if i should use assets instead. This will mean it's - as far as i know - not auto-updating on all instances like symbols, but you don't have them bound to single documents.

 

Or am i missing the point completely here? :D

[misc33]

I think it depends how complex the contents of each artboard. I regulary work with AD files that contain over 30 artboards with no problem at all. Each artboard typically contains a black line drawing, often complex with placed images.

[R C-R]

For what it is worth, I have opened a pdf version of a 469 page Honda owner's manual in Affinity Designer. The pdf is 30.5 MB. The pages are mostly text but there are some raster images & vector shapes as well. Every page has trim & registration marks comprised of around 200 objects, so it is a fairly complex document.

 

It takes about 25-30 seconds to open on my not particularly powerful iMac (specs below in my sig) but once it does I see a grid of each page as a separate artboard, so 469 artboards! When I zoom in on a part of the grid it can be a bit sluggish while redrawing the included pages but not as bad as I expected -- about 0.5 to 4 seconds, depending on the complexity of the pages.

 

Remarkably, Activity Monitor says AD is using less than 3 GB of memory for the whole thing, so even though I have only 8 GB installed on the iMac, there is still plenty of memory for other apps & processes.

[farbenfeuer]

Thanks for your input guys! :)

I guess i will just exclude bigger projects such as displays and big banners n such and make seperate files for them and keep using one file for each web and print per client and see where it takes me. ;)

 

Further feedback still appreciated though. Especially from the devs, if they maybe have a recommendation in this?!