[jira] [Commented] (GIRAPH-32) Implement benchmarks to evaluate the performance of message passing

2011-09-19 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/GIRAPH-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107794#comment-13107794
 ] 

Hudson commented on GIRAPH-32:
--

Integrated in Giraph-trunk-Commit #9 (See 
[https://builds.apache.org/job/Giraph-trunk-Commit/9/])
GIRAPH-32: Implement benchmarks to evaluate the performance of message 
passing

hyunsik : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1172605
Files : 
* /incubator/giraph/trunk/CHANGELOG
* 
/incubator/giraph/trunk/src/main/java/org/apache/giraph/benchmark/RandomMessageBenchmark.java


 Implement benchmarks to evaluate the performance of message passing 
 

 Key: GIRAPH-32
 URL: https://issues.apache.org/jira/browse/GIRAPH-32
 Project: Giraph
  Issue Type: Task
  Components: benchmark
Reporter: Hyunsik Choi
Assignee: Hyunsik Choi
 Fix For: 0.70.0

 Attachments: GIRAPH-32.patch, GIRAPH-32_2.patch


 Message passing framework plays an important role in Giraph.
 We need some benchmark programs to evaluate the improvement related to 
 message passing method.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (GIRAPH-32) Implement benchmarks to evaluate the performance of message passing

2011-09-19 Thread Hyunsik Choi (JIRA)

 [ 
https://issues.apache.org/jira/browse/GIRAPH-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hyunsik Choi resolved GIRAPH-32.


Resolution: Fixed

Because this issue got +1, I just committed.

 Implement benchmarks to evaluate the performance of message passing 
 

 Key: GIRAPH-32
 URL: https://issues.apache.org/jira/browse/GIRAPH-32
 Project: Giraph
  Issue Type: Task
  Components: benchmark
Reporter: Hyunsik Choi
Assignee: Hyunsik Choi
 Fix For: 0.70.0

 Attachments: GIRAPH-32.patch, GIRAPH-32_2.patch


 Message passing framework plays an important role in Giraph.
 We need some benchmark programs to evaluate the improvement related to 
 message passing method.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (GIRAPH-38) Change of website in team-list.html

2011-09-19 Thread Christian Kunz (JIRA)

 [ 
https://issues.apache.org/jira/browse/GIRAPH-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Kunz resolved GIRAPH-38.
--

Resolution: Fixed

 Change of website in team-list.html
 ---

 Key: GIRAPH-38
 URL: https://issues.apache.org/jira/browse/GIRAPH-38
 Project: Giraph
  Issue Type: Improvement
  Components: site
Reporter: Christian Kunz
Priority: Trivial

 Change of www.jybe-inc.com to jy.be

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (GIRAPH-21) Revise CODE_CONVENTIONS

2011-09-19 Thread Jakob Homan (JIRA)

[ 
https://issues.apache.org/jira/browse/GIRAPH-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13108157#comment-13108157
 ] 

Jakob Homan commented on GIRAPH-21:
---

+1.  This looks reasonable.

 Revise CODE_CONVENTIONS
 ---

 Key: GIRAPH-21
 URL: https://issues.apache.org/jira/browse/GIRAPH-21
 Project: Giraph
  Issue Type: Improvement
Reporter: Avery Ching
Assignee: Avery Ching
Priority: Minor
 Attachments: GIRAPH-21.diff


 Currently there is a CODE_CONVENTIONS file in the base path of Giraph.  It's 
 fairly sparse and we have been assuming an 80 char limit per line.  It's good 
 to have common conventions so that the code doesn't get too messy.  Does 
 anyone have any opinions on this now?  Probably best to tackle early and then 
 have something to follow.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (GIRAPH-21) Revise CODE_CONVENTIONS

2011-09-19 Thread Jakob Homan (JIRA)

 [ 
https://issues.apache.org/jira/browse/GIRAPH-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Homan resolved GIRAPH-21.
---

Resolution: Fixed

I've committed this. Resolving.

 Revise CODE_CONVENTIONS
 ---

 Key: GIRAPH-21
 URL: https://issues.apache.org/jira/browse/GIRAPH-21
 Project: Giraph
  Issue Type: Improvement
Reporter: Avery Ching
Assignee: Avery Ching
Priority: Minor
 Attachments: GIRAPH-21.diff


 Currently there is a CODE_CONVENTIONS file in the base path of Giraph.  It's 
 fairly sparse and we have been assuming an 80 char limit per line.  It's good 
 to have common conventions so that the code doesn't get too messy.  Does 
 anyone have any opinions on this now?  Probably best to tackle early and then 
 have something to follow.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (GIRAPH-40) Adding checkstyle enforcement of Giraph code conventions

2011-09-19 Thread Avery Ching (JIRA)
Adding checkstyle enforcement of Giraph code conventions


 Key: GIRAPH-40
 URL: https://issues.apache.org/jira/browse/GIRAPH-40
 Project: Giraph
  Issue Type: New Feature
Reporter: Avery Ching
Priority: Minor


Now that we have some code conventions (see GIRAPH-21), we should enforce them 
with a maven checkstyle plugin.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira