Is there anyway to make the publishing faster

Yes there are many ways to do this. 

Depending on your resources and how you want to approach this.

I would start with multiple workers per host and add additional queue sets. 

(taken from a PPT about 10 years old)

Multiple Worker per Host Configuration Guidance 
Memory must be able to support all of the worker processes simultaneous and may use the most concurrently when family table based assemblies are checked in
Typically the family table generic and its instances will align themselves sequentially in the publishing queues and may all come up for publishing simultaneously
• This condition can be constrained using Queue Sets which we will describe later in this presentation – Disks on the worker are needed to manage the local workspaces for the files that are getting downloaded by the workers
• You can spread the CAD Worker Setup directories across different disks on the host to span the IO out over multiple disks and avoid any throughput contention that a single disk may have
• Publish Queue Configurations
– In a typical installation customers may only have the standard High, Medium and Low publishing queues with no additional queue sets
– In standard configurations like this, additional PublisherQueue# entries should be created for each additional worker
• Ideally over configuring the number of PublisherQueue# queues by at least 20 to 40% will help improve throughput as jobs from the H,M,L queues can be placed in the next available PublisherQueue before the next worker becomes available. This results in less idle time on the worker so that it always has work to perform
• The ratios of queues to workers is somewhat subjective but this should give you a decent setting to start with until you can better calculate your average publishing speeds and throughput
– A system with 4 workers ideally should have PublisherQueue1 through 6 – A system with 10 workers should at least have PublisherQueue1 through 14 or 15.
– A system with 20 workers should have at least 25 and upwards of 30 or more
– A system with 40 workers should have at least 55 queues or more

https://www.ptc.com/en/support/article/CS43769

https://www.ptc.com/en/support/article/CS255203

Let me know if you need more info

Can you tell us what type of content is being published?  The tips and tricks to performance vary by application.

What are the business rules behind what is being published?  Publish on check in, recent migration, other?

Before getting into CAD Workers scalability and tuning, ensure the business requirements are met without publishing unnecessary content.  We want to 'right size' publishing.  That means not publishing on check in.  If necessary, enable manual job submission for unreleased content and let the users publish unreleased content when they really need to see it outside the native CAD system.  This will eliminate thousands of publish jobs for content that will never be viewed in Creo View.  It will help keep the database at a healthy size and slow the growth of the file vaults.

Is this 17k of unique pending publish jobs?  There aren't a bunch of repeat failures in the list and the same jobs (object name and version) aren't appearing multiple times?

Hi @AP_10697045,

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
Of course, if you have more to share on your issue, please pursue the conversation. 

Thanks,
Anurag