[Q] Question on Magma (or other Persistence Engine for Squeak/Seaside)

Sungjin Chun chunsj at embian.com
Thu Apr 19 07:11:46 UTC 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Muller wrote:
> The screenshot looks like the first opening page.  That would mean
> you're counting the time to do the initial Magma session connection.
> Does then selecting page 2 also take that long?
> 
> Further, what happens, after selecting page 2, if you go back ot page
> 1.  Is is still 1 second?

No, there's almost no difference; slow.
> 
> If so, you should profile, its probably Seaside or the Sushi demo
> itself, it ain't Magma..
> 

Following is my profiling result. I've only copied part of it.

[[90.6% {2342ms} WAAnswerHandler(WAPresenter)>>renderWithContext:
[[  90.6% {2342ms} WAAnswerHandler(WAPresenter)>>renderContentOn:
[[    90.6% {2342ms} WAStoreFillCart(WAPresenter)>>renderWithContext:
[[      90.6% {2342ms} WAStoreFillCart>>renderContentOn:
[[        89.6% {2316ms} WATableDataTag(WATagBrush)>>with:
[[          88.7% {2293ms} WATableDataTag(WATagBrush)>>within:
[[            88.7% {2293ms} WAStoreInfo(WAComponent)>>renderOn:
[[              88.7% {2293ms} WADelegation(WAPresenter)>>renderWithContext:
[[                88.7% {2293ms} WADelegation(WAPresenter)>>renderContentOn:
[[                  88.7% {2293ms}
WAAnswerHandler(WAPresenter)>>renderWithContext:
[[                    88.7% {2293ms}
WAAnswerHandler(WAPresenter)>>renderContentOn:
[[                      88.7% {2293ms}
WABatchSelection(WAPresenter)>>renderWithContext:
[[                        88.7% {2293ms} WABatchSelection>>renderContentOn:
[[                          44.7% {1155ms} WABatchedList>>batch
[[                            |23.5% {607ms}
MagmaCollectionReader>>copyFrom:to:
[[                            |  |23.5% {607ms} MagmaCollectionReader>>at:
[[[23.5% {607ms} MagmaCollectionReader>>at:ifOutOfBounds:
[[[  23.5% {607ms} MagmaCollectionReader>>primAt:ifOutOfBounds:
[[[    23.5% {607ms} MagmaCollectionReader>>loadFromIndex:pageSize:
[[[      23.5% {607ms} MagmaCollectionReader>>segmentContaining:
[[[        23.5% {607ms} MagmaCollectionReader>>refreshSegment:loadObjects:
[[[          23.5% {607ms}
MagmaCollection>>refreshSegment:where:...ze:using:loadObjects:
[[[            23.5% {607ms}
MagmaSession>>refreshSegment:of:where...ize:using:loadObjects:
[[[              23.0% {595ms} MagmaSession>>submit:
[[[                22.7% {587ms} MaLocalServerLink>>submit:
[[[                  22.7% {587ms}
MaLocalRequestServer(MaRequestServer)>>processRequest:
[[[                    22.7% {587ms} MagmaRepositoryController>>value:
[[[                      22.7% {587ms}
MagmaRepositoryController>>processRequest:
[[[                        22.7% {587ms} MaRefreshSegmentRequest>>process
[[[                          22.7% {587ms}
MaObjectRepository>>refreshSegmentIn:
[[[                            20.6% {533ms}
MagmaCollectionManager>>load:upTo:where:withObjects:except:


For me,
WABatchSelection>>renderContentOn:, WABatchedList>>batch and
MagmaCollectionReader>>copyFrom:to: are source of the problem. I cannot
pick specific one.

Thanks in advance.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGJxYyQqspS1+XJHgRAtXaAJ94dRa1WJ9Vli+kYI64hOcPFvDC5wCfVxig
Lt+ej5Ne389bEmOUxUxbnms=
=l192
-----END PGP SIGNATURE-----


More information about the Magma mailing list