On Tue, Dec 12, 2017 at 11:47 AM, Eno <tgkuo1@gmail.com> wrote:

My package�� TkIDE <http://smalltalkhub.com/#!/~tgkuo/TkIDE>�� ��relied on
object database, sandstone, to store the objects.

After upgrade to 6.1 on macOS, the save process became very slow.

Following the debugging process, I found the bottle neck is at this method,
FLSerialization>>analysisStep.



Hi Eno,

Well, its nothing strange analysisStep taking most of the time. That's usually the case as its the hardest part during serialization.��
What you should try is get deeper inside the analysisStep to see where the time is taken. Maybe you can realize a class or a cluster that's taking most of the time.
You can also analyze this way:

FileStream forceNewFileNamed: 'debug.fuel' do: [:aFile |
FLSerializer newDefault
setDebug;
serialize: myDatabaseObject on: aFile binary].

FLDebugSerialization last log inspect.


That will get you a log of all objects to be serialized and maybe you can see which cluster is getting too big.

Hope this helps.

��
I'm just a hobbyst, not acquainted with the system core and basis packages,
I cann't figure out what the cause, just guessing maybe my object is too
complicated to be serialized or the FLserialization really gets something
wrong.

Best reguards.

Eno




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html




--