Hi

The tomograph has not been tested/used for remote monitoring.
It requires an addition to its parser, but there is also no guarantee that
the message (blocks) received with trace information will not interfere

I would start the tomograph on the remote machine.
regards, Martin

On 9/17/13 3:07 AM, Mengmeng Chen wrote:
Hi,

We have a MAL function and we are trying to use tomograph to profile the execution of it when it is executed on a remote node. However, the tomograph fails right after the function is executed. We are just wondering if we did something wrong and if tomograph can work with a remote function call.

Here's what we want to do:

From node A, we run a MAL function,  which will execute a MAL function on both node A and node B using remote.exec() method.

 

Here's what we did and what happened: 

1. in A start mclient

 

2. in A and B, start tomograph "tomograph -d db1 -h localhost"

 

3. in A, start the driver function, which will call remote.exec for the MAL function on both A and B

 

Then, in A and B, tomograpg exits promptly

 

ubuntu@MC-MoDB1:~->tomograph -d db1 -h localhost

-- opened UDP profile stream MC-MoDB1:50010 for localhost

Created tomogram 'tomograph'

Run: 'gnuplot tomograph.gpl' to create the 'tomograph.pdf' file

The memory map is stored in 'tomograph.dat'

The trace is saved in 'tomograph.trace' for use with --trace option


Looking at the tomograph trace file generated on node B, we have something like:

 

9       1430    18111   17039   71      71      2       0       0       remote.connect           "X_22 := remote.connect(\"mapi:monetdb://192.168.4.4:50000/db1\",\"monetdb\",\"monetdb\",\"msql\");",   ]

11      1007    10501   9496    70      71      2       0       0       remote.connect           "X_24 := remote.connect(\"mapi:monetdb://192.168.5.4:50000/db1\",\"monetdb\",\"monetdb\",\"msql\");",   ]

69      23408   23605   198     72      72      2       0       0       remote.bintype           "remote.bintype();",    ]

11      10867   10867   0       71      71      5       0       0       profiler.wait             0.00  0.04  0.75  0.00  0.00  0.00  0.00  0.17  0.17  0.17  0.00  0.00  0.00  0.00  0.00  0.00  0.00  0.01  0.00  0.00  0.00  0.00  0.00  0.00  0.25  0.01  0.25  0.00  0.00  0.00  0.00  0.00

9       18497   18497   0       71      71      5       0       0       profiler.wait             0.00  0.04  0.75  0.00  0.00  0.00  0.00  0.17  0.17  0.17  0.00  0.00  0.00  0.00  0.00  0.00  0.00  0.01  0.00  0.00  0.00  0.00  0.00  0.00  0.25  0.01  0.25  0.00  0.00  0.00  0.00  0.00

69      23978   23978   0       72      72      4       0       0       profiler.ping             0.00  0.04  0.75  0.00  0.00  0.00  0.00  0.17  0.17  0.17  0.00  0.00  0.00  0.00  0.00  0.00  0.00  0.01  0.00  0.00  0.00  0.00  0.00  0.00  0.25  0.01  0.25  0.00  0.00  0.00  0.00  0.00

 

================================

 

on node A, the tomograph trace file looks like:

 

4       327     453     127     66      66      2       0       0       remote.bintype           "remote.bintype();",    ]

4       684     684     0       66      66      4       0       0       profiler.ping             0.15  0.15  0.15  0.15  0.15  0.15  0.15  0.15  0.15  0.17  0.15  0.15  0.15  0.15  0.15  0.17  0.15  0.25  0.15  0.15  0.15  0.15  0.15  0.15  0.15  0.20  0.17  0.15  0.15  0.15  0.15  0.15

 

================================



Any help would be appreciated!

Thanks,
Mengmeng





_______________________________________________
users-list mailing list
users-list@monetdb.org
http://mail.monetdb.org/mailman/listinfo/users-list