I'd use the ACS Commons Query Packager -- that way you can build you package based on the result set from a jcr-sql query.

RE -- 4) Removed all ./crx-quickstart/repository/segmentstore/*.bak files. That documentation really should be updated.  Deleting the .bak files is actually a poor idea and shouldn't be done until the instance is restored to a healthy state.Removing the bak files essentially ensures you can't recove...

RE : com.adobe.granite.auth.saml.util.SamlReader Signature verification failed for Either the Assertion or the Signature is missing from the SAMLRequest/SAMLResponse Capture a HAR containing the entire network trace of the logout and base-64 decrypt the POST data to understand what is messed up. 

104 is fine. This generally is not of concern until the jcr-session count goes into the thousands.

First check that this service user exists : translation-preview Second to that, log a ticket with Customer Care.   Quick inspection of the source code, the resolverFactory has got to be the null object...  It's trying to get the resource resolver for the above service user :  resolverFactory.getServ...

Long thread pause times strongly indicate that your Java heap is suffering from consecutive FullGC cycles unable to reclaim any space from OldGen. You will need : 1) gc.logs (if you have them) -- then you can use something like GCEasy (http://gceasy.io/) to visualize the heap state across time. This...

RE : we see a valid jcr:data Click on "View" which will download the binary as a file.Save it as "pic.png" and see if the image actually exists. I'd be interested to see if it's a 0-byte file.    

jcr:data is the actual binary object. So no - it did not successfully install.  You'd likely see a missing blob / datastore exception if something referenced this thumbnail rendition./content/dam/myproj/promotional/some-pages/brand-logos/puma-logo.png/jcr:content/renditions/cq5dam.thumbnail.319.319....

What does slowness mean to you? It is very subjective... Capture a series of thread dumps while things are 'slow' and use that as a starting point to better understand WHY it's slow. [1] - could be a product issue- could be an index issue -- eg a corruption, or perhaps heavy usage of apache tika tha...

Given that the screenshot is showing your own custom metadata schema I'd start by understanding what field your title maps to and ensure it's updating what you think it's updating.