remove ia pool.

[bluesky013]

Re: #

Changelog

• remove ia pool.

---

Continuous Integration

This pull request:

• needs automatic test cases check.

  Manual trigger with @cocos-robot run test cases afterward.

• does not change any runtime related code or build configuration

  If any reviewer thinks the CI checks are needed, please uncheck this option, then close and reopen the issue.

---

Compatibility Check

This pull request:

• changes public API, and have ensured backward compatibility with deprecated features.
• affects platform compatibility, e.g. system version, browser version, platform sdk version, platform toolchain, language version, hardware compatibility etc.
• affects file structure of the build package or build configuration which requires user project upgrade.
• introduces breaking changes, please list all changes, affected features and the scope of violation.

[bluesky013]

@cocos-robot run test cases

[github-actions]

Interface Check Report

This pull request does not change any public interfaces !

[github-actions]

@bluesky013, Please check the result of run test cases:

• Test Platform: PR-Test
• Editor Version: v3.8.1
• Task Result: FAIL
• Task URL: https://cctest.cocos.org/#/reportview/PR-TEST/96e86c89-a0cb-48ff-aaca-e5ba447b3fd7/-1
• GitHub Action: https://github.com/cocos/cocos-engine/actions/runs/5761326712

Task Details

Platform	build	boot	runned	crashScene	FailScene
web-mobile	PASS	PASS	FAIL
windows	PASS	PASS	FAIL		planar-shadow,material-upgrade,label-cacheMode,label-align,ttf-font
ios	PASS	PASS	FAIL
android	PASS	PASS	FAIL		planar-shadow,material-upgrade,rich-text-long-string-truncation
mac	PASS	PASS	FAIL		planar-shadow,material-upgrade

[github-actions]

@bluesky013, Please check the result of run test cases:

• Test Platform: PR-Test
• Editor Version: v3.8.1
• Task Result: FAIL
• Task URL: http://cctest.cocos.org/#/reportview/PR-TEST/c6683958-8352-4e93-8ab5-10a8c6fedd6d/-1
• GitHub Action: https://github.com/cocos/cocos-engine/actions/runs/5761910365

Task Details

Platform	build	boot	runned	crashScene	FailScene
web-mobile	PASS	PASS	PASS
windows	PASS	PASS	FAIL		planar-shadow,material-upgrade,label-cacheMode,label-align,ttf-font
ios	PASS	PASS	FAIL
android	PASS	PASS	FAIL		planar-shadow,material-upgrade,rich-text-long-string-truncation
mac	PASS	PASS	FAIL		planar-shadow,material-upgrade

[github-actions]

@bluesky013, Please check the result of run test cases:

• Test Platform: PR-Test
• Editor Version: v3.8.1
• Task Result: FAIL
• Task URL: http://cctest.cocos.org/#/reportview/PR-TEST/a32c5d76-8d93-42cb-8e15-3498313d2c7a/-1
• GitHub Action: https://github.com/cocos/cocos-engine/actions/runs/5768398914

Task Details

Platform	build	boot	runned	crashScene	FailScene
web-mobile	PASS	PASS	PASS
windows	PASS	PASS	FAIL		label-cacheMode,label-align,ttf-font
ios	PASS	PASS	FAIL
android	PASS	PASS	FAIL		rich-text-long-string-truncation
mac	PASS	PASS	FAIL		planar-shadow,material-upgrade

[SantyWang]

How about the performance? and InputAssembler has its own allocator?

[SantyWang]

Please use cocos-benchmark project(BunnyMark scene) to test 2D performance.

[bluesky013]

How about the performance? and InputAssembler has its own allocator?

The Input Assembler is a container for VertexBuffer and IndexBuffer. In the current 2D scenario, they both share the same VB and IB, so there is no need to create an additional IA for different drawInfo.

The Input Assembler should not be coupled with DrawInfo. Set drawInfo interface will be deprecated in 3.9. The correct usage should be as follows:

bindInputAssembler()
draw(0, 1)
draw(1, 2)
draw(2, 3)

There are no operations that would have a performance impact, and there is no allocator either. The DrawBatch2D simply maintains independent drawInfo.

[bluesky013]

cocos-benchmark

currently under testing.

[SantyWang]

The Input Assembler is a container for VertexBuffer and IndexBuffer. In the current 2D scenario, they both share the same VB and IB, so there is no need to create an additional IA for different drawInfo.

The Input Assembler should not be coupled with DrawInfo. Set drawInfo interface will be deprecated in 3.9. The correct usage should be as follows:

bindInputAssembler()
draw(0, 1)
draw(1, 2)
draw(2, 3)
There are no operations that would have a performance impact, and there is no allocator either. The DrawBatch2D simply maintains independent drawInfo.

I see.

[bluesky013]

Please use cocos-benchmark project(BunnyMark scene) to test 2D performance.

Tested:
Benchmark: BunnyTest （25000）

Env: Adreno (TM) 642L GLES3.2

before:

after

Seems no impact on performance.

[github-actions]

@bluesky013, Please check the result of run test cases:

• Test Platform: PR-Test
• Editor Version: v3.8.1
• Task Result: FAIL
• Task URL: http://cctest.cocos.org/#/reportview/PR-TEST/57032b09-8b46-4d58-afd6-ca72a6513bae/-1
• GitHub Action: https://github.com/cocos/cocos-engine/actions/runs/5793803898

Task Details

Platform	build	boot	runned	crashScene	FailScene
web-mobile	PASS	PASS	PASS
windows	PASS	PASS	FAIL		label-cacheMode,label-align,ttf-font
ios	PASS	PASS	FAIL	compressWithGray	compressWithGray
android	PASS	PASS	FAIL		rich-text-long-string-truncation
mac	PASS	PASS	FAIL		planar-shadow,material-upgrade

[bluesky013]

@cocos-robot run test cases

[github-actions]

@bluesky013, Please check the result of run test cases:

• Test Platform: PR-Test
• Editor Version: v3.8.1
• Task Result: FAIL
• Task URL: https://cctest.cocos.org/#/reportview/PR-TEST/8e665b86-ad11-42ad-b40d-9e929d89fdec/-1
• GitHub Action: https://github.com/cocos/cocos-engine/actions/runs/5804310473

Task Details

Platform	build	boot	runned	crashScene	FailScene
web-mobile	PASS	PASS	PASS
windows	PASS	PASS	FAIL		label-cacheMode,label-align,ttf-font
ios	FAIL		FAIL
android	PASS	PASS	FAIL		rich-text-long-string-truncation
mac	PASS	PASS	PASS