direct transaction is slow

[troyhp0632]

✅ SolanaTrade client initialized successfully!
Buying tokens from PumpSwap...
buy方法中swap之前耗时: 2.884µs
swap方法中execute parallel之前的耗时: 61.157µs
[SDK] Buy timing(after_submit) build_instructions: 0.06ms before_submit: 0.06ms submit: 614.10ms start_to_submit: 614178 μs
[SDK] Buy timing(after_confirm) confirm: 11881.40ms total: 12495.61ms
buy方法中swap耗时: 12.495646374s

[0xfnzero]

@troyhp0632 这只是统计的方式不一样，不用担心

[troyhp0632]

从目前我的交易上来看，我用postman手动进行买卖交易的话，这个时间确认很长，我用的是direct方式，因为我要做接口给我的其他服务使用。这个能是什么原因？

[troyhp0632]

原来旧版本的我改过一些东西，变的快了，现在我往了改了什么了，更新之后我看代码抽象了很多东西，具体什么地方需要修改也没时间搞了，所以就想问问作者，一般这种情况会发生在什么地方？

[0xfnzero]

@troyhp0632 直接交易因为需要去查询池子信息，你用速度快一点的RPC就会快很多

[adamantmm]

Your timing dump already localizes it: instruction build is ~0.06ms, submit ~614ms, confirm ~11.8s. So this is not SDK compute — it is landing + confirmation latency.

Things that usually move the needle on PumpSwap buys:

1. Priority fees / compute unit price — under contention, default fees sit in the queue; bumping CU price often cuts confirm time more than switching RPC.
2. RPC path — confirm against a low-latency provider close to your bot; some public endpoints are fine for send and terrible for confirm.
3. skipPreflight / commitment — if you confirm at finalized, expect multi-second tails; confirmed is enough for most trading loops, then reconcile.

If before_submit stays under 1ms after those changes, the SDK side is doing its job and the remaining time is chain/RPC.