Performance problem exploration for UIParticle plugin

[Bruce-DC]

Hello!
After a period of familiarity, we would like to apply your UIParticle plugin to our project to solve the problem of using too many Canvas components for UI particle effects in our project. However, during this time we also discovered a problem: when using THE UIParticle component to manage multiple particle effects in the UI, does it cause performance problems?
We downloaded your demo for research. Here we only compare UIParticle and SortingOrder, so the Hierarchy panel looks like this:

When we used only one UIParticle, the average frame rate was around 550 frames:

When we use only one SortingOrder, the average frame rate is around 600 frames:

It's not a big difference, but let's increase the number to 10.
When showing 10 UIParticles, the average frame rate is 270 frames:

When we show 10 sortingOrders, the average frame rate is still around 450:

At the same time, we can see that SortingOrder performs better in CPU usage, batch processing and other data.
Because there is a problem in our project that a page uses more than ten Canvas components to control the level of effects, we compare the experiment in this way.
Is it right to draw this conclusion? Or is it unscientific for us to compare?
We look forward to hearing from you.
Thank you very much!

[ifshuaishuai]

Yes, I also found that UIParticle performance badly, correct me if i am wrong.
So I recommend check out UIParticleSystem.

[midiphony]

In the README.md, the developer compared its approach with the aforementioned UIParticleSystem.

The issue author should maybe try this other system and compare.

Also, profiler data investigation might be more relevant !

[mob-sakai]

Sorry for my late reply.
SortingOrder approach is the fastest and most efficient way to operate.
Its approach works without any extra processes.
However, it requires some canvases with sorting order before and after the particle system.

[mob-sakai]

@Bruce-DC @ifshuaishuai @midiphony
Sorry for my late reply.

I test these approaches with a performance-test project.
"Mesh Sharing Group" feature, added in v4.0.0, performs better than "Sorting By Canvas" approach.
PerformanceTest.zip

It displays 300 "flame and spread effect (with Unity-chan)".

NOTE: Below are FPS and stat in Editor (MacOSX). Similar FPS was shown on my iPhone 6s.

Approach	FPS on Editor	FPS on iPhone6	FPS on Xperia XZ
Particle System	43	57	22
UIParticleSystem	4	3	0 (unmeasurable)
Sorting By Canvas	43	44	18
UIParticle	17	12	4
UIParticle with MeshSharing	44	45	30

Particle System (default)

UIParticleSystem

NOTE: UIParticleSystem does not support trail and texture animation

Sorting By Canvas

UIParticle (v3.3.12)

UIParticle (v4.0.0, without mesh sharing)

UIParticle (v4.0.0, with mesh sharing, 5 groups)

NOTE: The mesh sharing feature improves performance by sharing "particle simulation", "mesh baking", and "mesh combining".

[mob-sakai]

Since there has been no new discussion for a long time, this issue was closed.

If the same issue arises, please re-open this issue.