StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15478743
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-18T14:04:08.543
FavoriteCount
0
LastActivityDate
2013-03-18T14:20:10.807
LastEditDate
2013-03-18T14:20:10.807
LastEditorUserId
1245508
OwnerUserId
1245508
ParentId
9077145
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
My experiences with Gridgain told me, that the job definition is very important for the processing time. When you generate jobs with a small size, the communication overhead is large and all might be slowed (you might also run into other problems with result collect cache size or timeouts). when you on the other hand chose jobs in size too large, slow nodes may block the process while other nodes are idle. finding the best size to a job is difficult. job stealing may assist to distribute jobs better AFTER they were sent to the grid nodes. limiting the curently processed jobs to a number and enable the worker nodes to steal everything above this number of jobs in queue is done with the folloing code. this configuration is also possible with an xml file. <pre><code>public class ConfigGrid { // config jobStealing public static GridConfigurationAdapter JobStealing( GridConfigurationAdapter cfg, int waitJobsThreshold, int activeJobsThreshold, boolean stealingEnabled) { GridJobStealingCollisionSpi spi = new GridJobStealingCollisionSpi(); // Configure number of waiting jobs // in the queue for job stealing. spi.setWaitJobsThreshold(waitJobsThreshold); // Configure stealing attempts number. spi.setMaximumStealingAttempts(10); // Configure number of active jobs that are allowed to execute // in parallel. This number should usually be equal to the number // of threads in the pool (default is 100). spi.setActiveJobsThreshold(activeJobsThreshold); // Enable stealing. spi.setStealingEnabled(stealingEnabled); // Override default Collision SPI. cfg.setCollisionSpi(spi); return cfg; } </code></pre> in your main function, you call it then like: <pre><code>GridConfigurationAdapter cfg = new GridConfigurationAdapter(); // config job stealing cfg = ConfigGrid.JobStealing(cfg, numberOfJobs, setActiveJobs, stealingEnabled); GridFactory.start(cfg); </code></pre> for more settings read the documentation about GridJobStealingCollisionSpi. (edit: of course you must use the same settings on each node)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAuto discover the gridnode and share some jobs to the new grid which started at the middile of the jobs execution
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmojjj
UserOwnerUserId
1. USmojjj
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.