# abeh - Hey team!  I tried to generate this pcb....

Channel: #support
Source: https://discord.com/channels/1233487248129921135/1534286683107889303
Started: 2026-08-04T19:47:31.486000+00:00
Last activity: 2026-08-05T03:55:31.107000+00:00

## abeh — 2026-08-04T19:47:30.921000+00:00

Hey team!  I tried to generate this pcb.  Its a bit big, but it should be working and it takes 4h at the placement part. Is there a way to accelerate the autoplacement or all I need to do is buy a better CPU?
Attachment: message.txt — https://cdn.discordapp.com/attachments/1353415621995397172/1534286682478874664/message.txt?ex=6a739352&is=6a7241d2&hm=63fe43e81a286868708a0d40ef63ebfe6fa84f79ff13d11f99fad561dc8fb926&

## Seve — 2026-08-04T19:52:59.799000+00:00

The ahtorouting takes 4h?

## astrimid — 2026-08-04T19:59:56.213000+00:00

I wonder if there's some file format at lower level than circuitjson someone could git version

## Seve — 2026-08-04T20:43:43.263000+00:00

<@1525187702029549659> do you mean for caching the autorouting? In theory this could be done by committing `.tscircuit/cache`

## abeh — 2026-08-04T20:44:20.048000+00:00

well not even the routing. it like froze at the placement part

## abeh — 2026-08-04T20:44:33.733000+00:00

i even disabled the routing

## Seve — 2026-08-04T20:44:44.850000+00:00

that's very unusual

## abeh — 2026-08-04T20:44:51.710000+00:00

its 213 components tho so that might be why

## Seve — 2026-08-04T20:44:59.296000+00:00

it is likely a bug

## Seve — 2026-08-04T20:45:31.565000+00:00

we will get this resolved today, i'm a bit late getting on today but we'll fix it

## abeh — 2026-08-04T20:45:56.864000+00:00

ok all good thanks!

## Rishabh — 2026-08-05T01:36:37.654000+00:00

I can try to investigate this

## Rishabh — 2026-08-05T03:40:13.275000+00:00

Took 30sec to get the pcb preview, it was because of redundant `<trace />` elements, when the `connections={..}` on the components are already capturing the connectivity.

The packer converts port-to-port <trace /> into weightedConnections, which takes really long to compute as there are 825 such constraints

cc <@757706909351411845>
Attachment: image.png — https://community.tscircuit.com/media/1534405642771501076

## Rishabh — 2026-08-05T03:41:23.963000+00:00

Btw <@157839368453750784> I have cleaned up the type errors, cause the code which you shared had a lot of incorrect props name. You can use this if you want
Attachment: message.txt — https://cdn.discordapp.com/attachments/1534286683107889303/1534405939606851735/message.txt?ex=6a740263&is=6a72b0e3&hm=04a3008cbe2984ea67434b24c84de993d6f33b649ff8b49870efede97792f2bf&

## Seve — 2026-08-05T03:55:11.959000+00:00

oh wow, so basically calculate-packing was slow due to the traces- i bet there are other inefficiencies, i would love to have the solver PackInput for a repro where we could try to detect that

## Seve — 2026-08-05T03:55:31.107000+00:00

also having a timeout on the packsolver is not a bad idea (this would be done in core when the platformConfig has a timeout configured)