[VOTE] accept DirectMemory as new Apache Incubator podling
Hi all guys, I'm now calling a formal VOTE on the DirectMemory proposal located here: http://wiki.apache.org/incubator/DirectMemoryProposal Proposal text copied at the bottom of this email. VOTE close on Tuesday, October 4, early 7:30 AM CET. Please VOTE: [ ] +1 Accept DirectMemory into the Apache Incubator [ ] +0 Don't care [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... Thanks in advance for participating! All the best, have a nice day, Simo P.S. Here's my +1 http://people.apache.org/~simonetripodi/ http://www.99soft.org/ = DirectMemory = == Abstract == The following proposal is about Apache !DirectMemory, a Java !OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta !BigMemory) to enable caching of Java objects without degrading JVM performance == Proposal == !DirectMemory's main purpose is to to act as a second level cache (after a heap based one) able to store large amounts of data without filling up the Java heap and thus avoiding long garbage collection cycles. Although serialization has a runtime cost store/retrieve operations are in the sub-millisecond range being pretty acceptable in every usage scenario even as a first level cache and, most of all, outperforms heap storage when the count of the entries goes over a certain amount. !DirectMemory implements cache eviction based on a simple LFU (Least Frequently Used) algorythm and also on item expiration. Included in the box is a small set of utility classes to easily handle off-heap memory buffers. == Background == !DirectMemory is a project was born in the 2010 thanks to Raffaele P. Guidi initial effort under [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already licensed under the Apache License 2.0. == Rationale == The rationale behind !DirectMemory is bringing off-heap caching to the open source world, empowering FOSS developers and products with a tool that enables breaking the heap barrier and override the JVM garbage collection mechanism collection - which could be useful in scenarios where RAM needs are over the usual limits (more than 8, 12, 24gb) and to ease usage of off-heap memory in general = Current Status = == Meritocracy == As a majority of the initial project members are existing ASF committers, we recognize the desirability of running the project as a meritocracy. We are eager to engage other members of the community and operate to the standard of meritocracy that Apache emphasizes; we believe this is the most effective method of growing our community and enabling widespread adoption. == Core Developers == In alphabetical order: * Christian Grobmeier * Maurizio Cucchiara * Olivier Lamy * Raffaele P. Guidi * Simone Gianni * Simone Tripodi * Tommaso Teofili == Alignment == The purpose of the project is to develop and maintain !DirectMemory implementation that can be used by other Apache projects. = Known Risks = == Orphaned Products == !DirectMemory does not have any reported production usage, yet, but is getting traction with developers and being evaluated by potential users and thus the risks of it being orphaned are minimal == Inexperience with Open Source == All of the committers have experience working in one or more open source projects inside and outside ASF. == Homogeneous Developers == The list of initial committers are geographically distributed across the Europe with no one company being associated with a majority of the developers. Many of these initial developers are experienced Apache committers already and all are experienced with working in distributed development communities. == Reliance on Salaried Developers == To the best of our knowledge, none of the initial committers are being paid to develop code for this project. == Relationships with Other Apache Products == !DirectMemory fits naturally in the ASF because it could be successfully employed together with a large number of ASF products ranging from JCS - as a new cache region between the heap and indexed file ones, to ORM systems like Cayenne (i.e. replacing current OSCache based implementation), Apache JDO and JPA implementations and also java based databases (i.e. Derby) and all systems managing large amounts of data from Hadoop to Cassandra == A Excessive Fascination with the Apache Brand == While the Apache Software Foundation would be a good home for the !DirectMemory project it already has some traction and it could live on its own - however we see reciprocal benefits for both the ASF and the project in adopting the brand to better reach the community = Documentation = 1. [[https://github.com/raffaeleguidi/DirectMemory|The original DirectMemory HomePage]] 2. [[https://github.com/raffaeleguidi/DirectMemory/wiki|The original DirectMemory Wiki]] 3. [[https://github.com/raffaeleguidi/DirectMemory/issues|The DirectMemory Issue Tracker (used also for enhancements, feature requests and discussion)]] = Initial Source = The intial sour
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 (binding) On Sun, Oct 2, 2011 at 9:36 AM, Simone Tripodi wrote: > Hi all guys, > > I'm now calling a formal VOTE on the DirectMemory proposal located here: > > http://wiki.apache.org/incubator/DirectMemoryProposal > > Proposal text copied at the bottom of this email. > > VOTE close on Tuesday, October 4, early 7:30 AM CET. > > Please VOTE: > > [ ] +1 Accept DirectMemory into the Apache Incubator > [ ] +0 Don't care > [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... > > Thanks in advance for participating! > > All the best, have a nice day, > Simo > > P.S. Here's my +1 > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > = DirectMemory = > > == Abstract == > The following proposal is about Apache !DirectMemory, a Java > !OpenSource multi-layered cache implementation featuring off-heap > memory storage (a-la Terracotta !BigMemory) to enable caching of Java > objects without degrading JVM performance > > == Proposal == > !DirectMemory's main purpose is to to act as a second level cache > (after a heap based one) able to store large amounts of data without > filling up the Java heap and thus avoiding long garbage collection > cycles. Although serialization has a runtime cost store/retrieve > operations are in the sub-millisecond range being pretty acceptable in > every usage scenario even as a first level cache and, most of all, > outperforms heap storage when the count of the entries goes over a > certain amount. !DirectMemory implements cache eviction based on a > simple LFU (Least Frequently Used) algorythm and also on item > expiration. Included in the box is a small set of utility classes to > easily handle off-heap memory buffers. > > == Background == > !DirectMemory is a project was born in the 2010 thanks to Raffaele P. > Guidi initial effort under > [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already > licensed under the Apache License 2.0. > > == Rationale == > The rationale behind !DirectMemory is bringing off-heap caching to the > open source world, empowering FOSS developers and products with a tool > that enables breaking the heap barrier and override the JVM garbage > collection mechanism collection - which could be useful in scenarios > where RAM needs are over the usual limits (more than 8, 12, 24gb) and > to ease usage of off-heap memory in general > > = Current Status = > > == Meritocracy == > As a majority of the initial project members are existing ASF > committers, we recognize the desirability of running the project as a > meritocracy. We are eager to engage other members of the community > and operate to the standard of meritocracy that Apache emphasizes; we > believe this is the most effective method of growing our community and > enabling widespread adoption. > > == Core Developers == > In alphabetical order: > > * Christian Grobmeier > * Maurizio Cucchiara > * Olivier Lamy > * Raffaele P. Guidi > * Simone Gianni > * Simone Tripodi > * Tommaso Teofili > > == Alignment == > The purpose of the project is to develop and maintain !DirectMemory > implementation that can be used by other Apache projects. > > = Known Risks = > == Orphaned Products == > !DirectMemory does not have any reported production usage, yet, but is > getting traction with developers and being evaluated by potential > users and thus the risks of it being orphaned are minimal > > == Inexperience with Open Source == > All of the committers have experience working in one or more open > source projects inside and outside ASF. > > == Homogeneous Developers == > The list of initial committers are geographically distributed across > the Europe with no one company being associated with a majority of the > developers. Many of these initial developers are experienced Apache > committers already and all are experienced with working in distributed > development communities. > > == Reliance on Salaried Developers == > To the best of our knowledge, none of the initial committers are being > paid to develop code for this project. > > == Relationships with Other Apache Products == > !DirectMemory fits naturally in the ASF because it could be > successfully employed together with a large number of ASF products > ranging from JCS - as a new cache region between the heap and indexed > file ones, to ORM systems like Cayenne (i.e. replacing current OSCache > based implementation), Apache JDO and JPA implementations and also > java based databases (i.e. Derby) and all systems managing large > amounts of data from Hadoop to Cassandra > > == A Excessive Fascination with the Apache Brand == > While the Apache Software Foundation would be a good home for the > !DirectMemory project it already has some traction and it could live > on its own - however we see reciprocal benefits for both the ASF and > the project in adopting the brand to better reach the community > > = Documentation = > 1. [[https://github.com/raffaeleguidi/DirectMemory|The original > DirectMemo
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 Maurizio Cucchiara Il giorno 02/ott/2011 10.45, "Christian Grobmeier" ha scritto: > +1 (binding) > > > On Sun, Oct 2, 2011 at 9:36 AM, Simone Tripodi wrote: >> Hi all guys, >> >> I'm now calling a formal VOTE on the DirectMemory proposal located here: >> >> http://wiki.apache.org/incubator/DirectMemoryProposal >> >> Proposal text copied at the bottom of this email. >> >> VOTE close on Tuesday, October 4, early 7:30 AM CET. >> >> Please VOTE: >> >> [ ] +1 Accept DirectMemory into the Apache Incubator >> [ ] +0 Don't care >> [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... >> >> Thanks in advance for participating! >> >> All the best, have a nice day, >> Simo >> >> P.S. Here's my +1 >> >> http://people.apache.org/~simonetripodi/ >> http://www.99soft.org/ >> >> = DirectMemory = >> >> == Abstract == >> The following proposal is about Apache !DirectMemory, a Java >> !OpenSource multi-layered cache implementation featuring off-heap >> memory storage (a-la Terracotta !BigMemory) to enable caching of Java >> objects without degrading JVM performance >> >> == Proposal == >> !DirectMemory's main purpose is to to act as a second level cache >> (after a heap based one) able to store large amounts of data without >> filling up the Java heap and thus avoiding long garbage collection >> cycles. Although serialization has a runtime cost store/retrieve >> operations are in the sub-millisecond range being pretty acceptable in >> every usage scenario even as a first level cache and, most of all, >> outperforms heap storage when the count of the entries goes over a >> certain amount. !DirectMemory implements cache eviction based on a >> simple LFU (Least Frequently Used) algorythm and also on item >> expiration. Included in the box is a small set of utility classes to >> easily handle off-heap memory buffers. >> >> == Background == >> !DirectMemory is a project was born in the 2010 thanks to Raffaele P. >> Guidi initial effort under >> [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already >> licensed under the Apache License 2.0. >> >> == Rationale == >> The rationale behind !DirectMemory is bringing off-heap caching to the >> open source world, empowering FOSS developers and products with a tool >> that enables breaking the heap barrier and override the JVM garbage >> collection mechanism collection - which could be useful in scenarios >> where RAM needs are over the usual limits (more than 8, 12, 24gb) and >> to ease usage of off-heap memory in general >> >> = Current Status = >> >> == Meritocracy == >> As a majority of the initial project members are existing ASF >> committers, we recognize the desirability of running the project as a >> meritocracy. We are eager to engage other members of the community >> and operate to the standard of meritocracy that Apache emphasizes; we >> believe this is the most effective method of growing our community and >> enabling widespread adoption. >> >> == Core Developers == >> In alphabetical order: >> >> * Christian Grobmeier >> * Maurizio Cucchiara >> * Olivier Lamy >> * Raffaele P. Guidi >> * Simone Gianni >> * Simone Tripodi >> * Tommaso Teofili >> >> == Alignment == >> The purpose of the project is to develop and maintain !DirectMemory >> implementation that can be used by other Apache projects. >> >> = Known Risks = >> == Orphaned Products == >> !DirectMemory does not have any reported production usage, yet, but is >> getting traction with developers and being evaluated by potential >> users and thus the risks of it being orphaned are minimal >> >> == Inexperience with Open Source == >> All of the committers have experience working in one or more open >> source projects inside and outside ASF. >> >> == Homogeneous Developers == >> The list of initial committers are geographically distributed across >> the Europe with no one company being associated with a majority of the >> developers. Many of these initial developers are experienced Apache >> committers already and all are experienced with working in distributed >> development communities. >> >> == Reliance on Salaried Developers == >> To the best of our knowledge, none of the initial committers are being >> paid to develop code for this project. >> >> == Relationships with Other Apache Products == >> !DirectMemory fits naturally in the ASF because it could be >> successfully employed together with a large number of ASF products >> ranging from JCS - as a new cache region between the heap and indexed >> file ones, to ORM systems like Cayenne (i.e. replacing current OSCache >> based implementation), Apache JDO and JPA implementations and also >> java based databases (i.e. Derby) and all systems managing large >> amounts of data from Hadoop to Cassandra >> >> == A Excessive Fascination with the Apache Brand == >> While the Apache Software Foundation would be a good home for the >> !DirectMemory project it already has some traction and it could live >> on its own - however w
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 (binding) -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Simone Tripodi" To: Subject: [VOTE] accept DirectMemory as new Apache Incubator podling Date: Sun, Oct 2, 2011 9:36 am Hi all guys, I'm now calling a formal VOTE on the DirectMemory proposal located here: http://wiki.apache.org/incubator/DirectMemoryProposal Proposal text copied at the bottom of this email. VOTE close on Tuesday, October 4, early 7:30 AM CET. Please VOTE: [ ] +1 Accept DirectMemory into the Apache Incubator [ ] +0 Don't care [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... Thanks in advance for participating! All the best, have a nice day, Simo P.S. Here's my +1 http://people.apache.org/~simonetripodi/ http://www.99soft.org/ = DirectMemory = == Abstract == The following proposal is about Apache !DirectMemory, a Java !OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta !BigMemory) to enable caching of Java objects without degrading JVM performance == Proposal == !DirectMemory's main purpose is to to act as a second level cache (after a heap based one) able to store large amounts of data without filling up the Java heap and thus avoiding long garbage collection cycles. Although serialization has a runtime cost store/retrieve operations are in the sub-millisecond range being pretty acceptable in every usage scenario even as a first level cache and, most of all, outperforms heap storage when the count of the entries goes over a certain amount. !DirectMemory implements cache eviction based on a simple LFU (Least Frequently Used) algorythm and also on item expiration. Included in the box is a small set of utility classes to easily handle off-heap memory buffers. == Background == !DirectMemory is a project was born in the 2010 thanks to Raffaele P. Guidi initial effort under [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already licensed under the Apache License 2.0. == Rationale == The rationale behind !DirectMemory is bringing off-heap caching to the open source world, empowering FOSS developers and products with a tool that enables breaking the heap barrier and override the JVM garbage collection mechanism collection - which could be useful in scenarios where RAM needs are over the usual limits (more than 8, 12, 24gb) and to ease usage of off-heap memory in general = Current Status = == Meritocracy == As a majority of the initial project members are existing ASF committers, we recognize the desirability of running the project as a meritocracy. We are eager to engage other members of the community and operate to the standard of meritocracy that Apache emphasizes; we believe this is the most effective method of growing our community and enabling widespread adoption. == Core Developers == In alphabetical order: * Christian Grobmeier * Maurizio Cucchiara * Olivier Lamy * Raffaele P. Guidi * Simone Gianni * Simone Tripodi * Tommaso Teofili == Alignment == The purpose of the project is to develop and maintain !DirectMemory implementation that can be used by other Apache projects. = Known Risks = == Orphaned Products == !DirectMemory does not have any reported production usage, yet, but is getting traction with developers and being evaluated by potential users and thus the risks of it being orphaned are minimal == Inexperience with Open Source == All of the committers have experience working in one or more open source projects inside and outside ASF. == Homogeneous Developers == The list of initial committers are geographically distributed across the Europe with no one company being associated with a majority of the developers. Many of these initial developers are experienced Apache committers already and all are experienced with working in distributed development communities. == Reliance on Salaried Developers == To the best of our knowledge, none of the initial committers are being paid to develop code for this project. == Relationships with Other Apache Products == !DirectMemory fits naturally in the ASF because it could be successfully employed together with a large number of ASF products ranging from JCS - as a new cache region between the heap and indexed file ones, to ORM systems like Cayenne (i.e. replacing current OSCache based implementation), Apache JDO and JPA implementations and also java based databases (i.e. Derby) and all systems managing large amounts of data from Hadoop to Cassandra == A Excessive Fascination with the Apache Brand == While the Apache Software Foundation would be a good home for the !DirectMemory project it already has some traction and it could live on its own - however we see reciprocal benefits for both the ASF and the project in adopting the brand to better reach the community = Documentation = 1. [[https://github.com/raffaeleguidi/DirectMemory|The original DirectMemory HomePage]] 2. [[ht
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 On Sun, Oct 2, 2011 at 1:06 PM, Simone Tripodi wrote: > Hi all guys, > > I'm now calling a formal VOTE on the DirectMemory proposal located here: > > http://wiki.apache.org/incubator/DirectMemoryProposal > > Proposal text copied at the bottom of this email. > > VOTE close on Tuesday, October 4, early 7:30 AM CET. > > Please VOTE: > > [ ] +1 Accept DirectMemory into the Apache Incubator > [ ] +0 Don't care > [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... > > Thanks in advance for participating! > > All the best, have a nice day, > Simo > > P.S. Here's my +1 > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > = DirectMemory = > > == Abstract == > The following proposal is about Apache !DirectMemory, a Java > !OpenSource multi-layered cache implementation featuring off-heap > memory storage (a-la Terracotta !BigMemory) to enable caching of Java > objects without degrading JVM performance > > == Proposal == > !DirectMemory's main purpose is to to act as a second level cache > (after a heap based one) able to store large amounts of data without > filling up the Java heap and thus avoiding long garbage collection > cycles. Although serialization has a runtime cost store/retrieve > operations are in the sub-millisecond range being pretty acceptable in > every usage scenario even as a first level cache and, most of all, > outperforms heap storage when the count of the entries goes over a > certain amount. !DirectMemory implements cache eviction based on a > simple LFU (Least Frequently Used) algorythm and also on item > expiration. Included in the box is a small set of utility classes to > easily handle off-heap memory buffers. > > == Background == > !DirectMemory is a project was born in the 2010 thanks to Raffaele P. > Guidi initial effort under > [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already > licensed under the Apache License 2.0. > > == Rationale == > The rationale behind !DirectMemory is bringing off-heap caching to the > open source world, empowering FOSS developers and products with a tool > that enables breaking the heap barrier and override the JVM garbage > collection mechanism collection - which could be useful in scenarios > where RAM needs are over the usual limits (more than 8, 12, 24gb) and > to ease usage of off-heap memory in general > > = Current Status = > > == Meritocracy == > As a majority of the initial project members are existing ASF > committers, we recognize the desirability of running the project as a > meritocracy. We are eager to engage other members of the community > and operate to the standard of meritocracy that Apache emphasizes; we > believe this is the most effective method of growing our community and > enabling widespread adoption. > > == Core Developers == > In alphabetical order: > > * Christian Grobmeier > * Maurizio Cucchiara > * Olivier Lamy > * Raffaele P. Guidi > * Simone Gianni > * Simone Tripodi > * Tommaso Teofili > > == Alignment == > The purpose of the project is to develop and maintain !DirectMemory > implementation that can be used by other Apache projects. > > = Known Risks = > == Orphaned Products == > !DirectMemory does not have any reported production usage, yet, but is > getting traction with developers and being evaluated by potential > users and thus the risks of it being orphaned are minimal > > == Inexperience with Open Source == > All of the committers have experience working in one or more open > source projects inside and outside ASF. > > == Homogeneous Developers == > The list of initial committers are geographically distributed across > the Europe with no one company being associated with a majority of the > developers. Many of these initial developers are experienced Apache > committers already and all are experienced with working in distributed > development communities. > > == Reliance on Salaried Developers == > To the best of our knowledge, none of the initial committers are being > paid to develop code for this project. > > == Relationships with Other Apache Products == > !DirectMemory fits naturally in the ASF because it could be > successfully employed together with a large number of ASF products > ranging from JCS - as a new cache region between the heap and indexed > file ones, to ORM systems like Cayenne (i.e. replacing current OSCache > based implementation), Apache JDO and JPA implementations and also > java based databases (i.e. Derby) and all systems managing large > amounts of data from Hadoop to Cassandra > > == A Excessive Fascination with the Apache Brand == > While the Apache Software Foundation would be a good home for the > !DirectMemory project it already has some traction and it could live > on its own - however we see reciprocal benefits for both the ASF and > the project in adopting the brand to better reach the community > > = Documentation = > 1. [[https://github.com/raffaeleguidi/DirectMemory|The original > DirectMemory HomePage
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 --tim On Sunday, October 2, 2011, Ashish wrote: > +1 > > On Sun, Oct 2, 2011 at 1:06 PM, Simone Tripodi wrote: >> Hi all guys, >> >> I'm now calling a formal VOTE on the DirectMemory proposal located here: >> >> http://wiki.apache.org/incubator/DirectMemoryProposal >> >> Proposal text copied at the bottom of this email. >> >> VOTE close on Tuesday, October 4, early 7:30 AM CET. >> >> Please VOTE: >> >> [ ] +1 Accept DirectMemory into the Apache Incubator >> [ ] +0 Don't care >> [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... >> >> Thanks in advance for participating! >> >> All the best, have a nice day, >> Simo >> >> P.S. Here's my +1 >> >> http://people.apache.org/~simonetripodi/ >> http://www.99soft.org/ >> >> = DirectMemory = >> >> == Abstract == >> The following proposal is about Apache !DirectMemory, a Java >> !OpenSource multi-layered cache implementation featuring off-heap >> memory storage (a-la Terracotta !BigMemory) to enable caching of Java >> objects without degrading JVM performance >> >> == Proposal == >> !DirectMemory's main purpose is to to act as a second level cache >> (after a heap based one) able to store large amounts of data without >> filling up the Java heap and thus avoiding long garbage collection >> cycles. Although serialization has a runtime cost store/retrieve >> operations are in the sub-millisecond range being pretty acceptable in >> every usage scenario even as a first level cache and, most of all, >> outperforms heap storage when the count of the entries goes over a >> certain amount. !DirectMemory implements cache eviction based on a >> simple LFU (Least Frequently Used) algorythm and also on item >> expiration. Included in the box is a small set of utility classes to >> easily handle off-heap memory buffers. >> >> == Background == >> !DirectMemory is a project was born in the 2010 thanks to Raffaele P. >> Guidi initial effort under >> [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub < https://github.com/raffaeleguidi/!DirectMemory/%7CGitHub>]] and already >> licensed under the Apache License 2.0. >> >> == Rationale == >> The rationale behind !DirectMemory is bringing off-heap caching to the >> open source world, empowering FOSS developers and products with a tool >> that enables breaking the heap barrier and override the JVM garbage >> collection mechanism collection - which could be useful in scenarios >> where RAM needs are over the usual limits (more than 8, 12, 24gb) and >> to ease usage of off-heap memory in general >> >> = Current Status = >> >> == Meritocracy == >> As a majority of the initial project members are existing ASF >> committers, we recognize the desirability of running the project as a >> meritocracy. We are eager to engage other members of the community >> and operate to the standard of meritocracy that Apache emphasizes; we >> believe this is the most effective method of growing our community and >> enabling widespread adoption. >> >> == Core Developers == >> In alphabetical order: >> >> * Christian Grobmeier >> * Maurizio Cucchiara >> * Olivier Lamy >> * Raffaele P. Guidi >> * Simone Gianni >> * Simone Tripodi >> * Tommaso Teofili >> >> == Alignment == >> The purpose of the project is to develop and maintain !DirectMemory >> implementation that can be used by other Apache projects. >> >> = Known Risks = >> == Orphaned Products == >> !DirectMemory does not have any reported production usage, yet, but is >> getting traction with developers and being evaluated by potential >> users and thus the risks of it being orphaned are minimal >> >> == Inexperience with Open Source == >> All of the committers have experience working in one or more open >> source projects insi-- > thanks > ashish > > Blog: http://www.ashishpaliwal.com/blog > My Photo Galleries: http://www.pbase.com/ashishpaliwal > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 On Sun, Oct 2, 2011 at 4:44 AM, Christian Grobmeier wrote: > +1 (binding) > > > On Sun, Oct 2, 2011 at 9:36 AM, Simone Tripodi > wrote: >> Hi all guys, >> >> I'm now calling a formal VOTE on the DirectMemory proposal located here: >> >> http://wiki.apache.org/incubator/DirectMemoryProposal >> >> Proposal text copied at the bottom of this email. >> >> VOTE close on Tuesday, October 4, early 7:30 AM CET. >> >> Please VOTE: >> >> [ ] +1 Accept DirectMemory into the Apache Incubator >> [ ] +0 Don't care >> [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... >> >> Thanks in advance for participating! >> >> All the best, have a nice day, >> Simo >> >> P.S. Here's my +1 >> >> http://people.apache.org/~simonetripodi/ >> http://www.99soft.org/ >> >> = DirectMemory = >> >> == Abstract == >> The following proposal is about Apache !DirectMemory, a Java >> !OpenSource multi-layered cache implementation featuring off-heap >> memory storage (a-la Terracotta !BigMemory) to enable caching of Java >> objects without degrading JVM performance >> >> == Proposal == >> !DirectMemory's main purpose is to to act as a second level cache >> (after a heap based one) able to store large amounts of data without >> filling up the Java heap and thus avoiding long garbage collection >> cycles. Although serialization has a runtime cost store/retrieve >> operations are in the sub-millisecond range being pretty acceptable in >> every usage scenario even as a first level cache and, most of all, >> outperforms heap storage when the count of the entries goes over a >> certain amount. !DirectMemory implements cache eviction based on a >> simple LFU (Least Frequently Used) algorythm and also on item >> expiration. Included in the box is a small set of utility classes to >> easily handle off-heap memory buffers. >> >> == Background == >> !DirectMemory is a project was born in the 2010 thanks to Raffaele P. >> Guidi initial effort under >> [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already >> licensed under the Apache License 2.0. >> >> == Rationale == >> The rationale behind !DirectMemory is bringing off-heap caching to the >> open source world, empowering FOSS developers and products with a tool >> that enables breaking the heap barrier and override the JVM garbage >> collection mechanism collection - which could be useful in scenarios >> where RAM needs are over the usual limits (more than 8, 12, 24gb) and >> to ease usage of off-heap memory in general >> >> = Current Status = >> >> == Meritocracy == >> As a majority of the initial project members are existing ASF >> committers, we recognize the desirability of running the project as a >> meritocracy. We are eager to engage other members of the community >> and operate to the standard of meritocracy that Apache emphasizes; we >> believe this is the most effective method of growing our community and >> enabling widespread adoption. >> >> == Core Developers == >> In alphabetical order: >> >> * Christian Grobmeier >> * Maurizio Cucchiara >> * Olivier Lamy >> * Raffaele P. Guidi >> * Simone Gianni >> * Simone Tripodi >> * Tommaso Teofili >> >> == Alignment == >> The purpose of the project is to develop and maintain !DirectMemory >> implementation that can be used by other Apache projects. >> >> = Known Risks = >> == Orphaned Products == >> !DirectMemory does not have any reported production usage, yet, but is >> getting traction with developers and being evaluated by potential >> users and thus the risks of it being orphaned are minimal >> >> == Inexperience with Open Source == >> All of the committers have experience working in one or more open >> source projects inside and outside ASF. >> >> == Homogeneous Developers == >> The list of initial committers are geographically distributed across >> the Europe with no one company being associated with a majority of the >> developers. Many of these initial developers are experienced Apache >> committers already and all are experienced with working in distributed >> development communities. >> >> == Reliance on Salaried Developers == >> To the best of our knowledge, none of the initial committers are being >> paid to develop code for this project. >> >> == Relationships with Other Apache Products == >> !DirectMemory fits naturally in the ASF because it could be >> successfully employed together with a large number of ASF products >> ranging from JCS - as a new cache region between the heap and indexed >> file ones, to ORM systems like Cayenne (i.e. replacing current OSCache >> based implementation), Apache JDO and JPA implementations and also >> java based databases (i.e. Derby) and all systems managing large >> amounts of data from Hadoop to Cassandra >> >> == A Excessive Fascination with the Apache Brand == >> While the Apache Software Foundation would be a good home for the >> !DirectMemory project it already has some traction and it could live >> on its own - however we see reciprocal bene
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 (non-binding) On Oct 2, 2011, at 3:36, Simone Tripodi wrote: > Hi all guys, > > I'm now calling a formal VOTE on the DirectMemory proposal located here: > > http://wiki.apache.org/incubator/DirectMemoryProposal > > Proposal text copied at the bottom of this email. > > VOTE close on Tuesday, October 4, early 7:30 AM CET. > > Please VOTE: > > [ ] +1 Accept DirectMemory into the Apache Incubator > [ ] +0 Don't care > [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... > > Thanks in advance for participating! > > All the best, have a nice day, > Simo > > P.S. Here's my +1 > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > = DirectMemory = > > == Abstract == > The following proposal is about Apache !DirectMemory, a Java > !OpenSource multi-layered cache implementation featuring off-heap > memory storage (a-la Terracotta !BigMemory) to enable caching of Java > objects without degrading JVM performance > > == Proposal == > !DirectMemory's main purpose is to to act as a second level cache > (after a heap based one) able to store large amounts of data without > filling up the Java heap and thus avoiding long garbage collection > cycles. Although serialization has a runtime cost store/retrieve > operations are in the sub-millisecond range being pretty acceptable in > every usage scenario even as a first level cache and, most of all, > outperforms heap storage when the count of the entries goes over a > certain amount. !DirectMemory implements cache eviction based on a > simple LFU (Least Frequently Used) algorythm and also on item > expiration. Included in the box is a small set of utility classes to > easily handle off-heap memory buffers. > > == Background == > !DirectMemory is a project was born in the 2010 thanks to Raffaele P. > Guidi initial effort under > [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already > licensed under the Apache License 2.0. > > == Rationale == > The rationale behind !DirectMemory is bringing off-heap caching to the > open source world, empowering FOSS developers and products with a tool > that enables breaking the heap barrier and override the JVM garbage > collection mechanism collection - which could be useful in scenarios > where RAM needs are over the usual limits (more than 8, 12, 24gb) and > to ease usage of off-heap memory in general > > = Current Status = > > == Meritocracy == > As a majority of the initial project members are existing ASF > committers, we recognize the desirability of running the project as a > meritocracy. We are eager to engage other members of the community > and operate to the standard of meritocracy that Apache emphasizes; we > believe this is the most effective method of growing our community and > enabling widespread adoption. > > == Core Developers == > In alphabetical order: > > * Christian Grobmeier > * Maurizio Cucchiara > * Olivier Lamy > * Raffaele P. Guidi > * Simone Gianni > * Simone Tripodi > * Tommaso Teofili > > == Alignment == > The purpose of the project is to develop and maintain !DirectMemory > implementation that can be used by other Apache projects. > > = Known Risks = > == Orphaned Products == > !DirectMemory does not have any reported production usage, yet, but is > getting traction with developers and being evaluated by potential > users and thus the risks of it being orphaned are minimal > > == Inexperience with Open Source == > All of the committers have experience working in one or more open > source projects inside and outside ASF. > > == Homogeneous Developers == > The list of initial committers are geographically distributed across > the Europe with no one company being associated with a majority of the > developers. Many of these initial developers are experienced Apache > committers already and all are experienced with working in distributed > development communities. > > == Reliance on Salaried Developers == > To the best of our knowledge, none of the initial committers are being > paid to develop code for this project. > > == Relationships with Other Apache Products == > !DirectMemory fits naturally in the ASF because it could be > successfully employed together with a large number of ASF products > ranging from JCS - as a new cache region between the heap and indexed > file ones, to ORM systems like Cayenne (i.e. replacing current OSCache > based implementation), Apache JDO and JPA implementations and also > java based databases (i.e. Derby) and all systems managing large > amounts of data from Hadoop to Cassandra > > == A Excessive Fascination with the Apache Brand == > While the Apache Software Foundation would be a good home for the > !DirectMemory project it already has some traction and it could live > on its own - however we see reciprocal benefits for both the ASF and > the project in adopting the brand to better reach the community > > = Documentation = > 1. [[https://github.com/raffaeleguidi/DirectMemory|The ori
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 (binding) Ralph On Oct 2, 2011, at 12:36 AM, Simone Tripodi wrote: > Hi all guys, > > I'm now calling a formal VOTE on the DirectMemory proposal located here: > > http://wiki.apache.org/incubator/DirectMemoryProposal > > Proposal text copied at the bottom of this email. > > VOTE close on Tuesday, October 4, early 7:30 AM CET. > > Please VOTE: > > [ ] +1 Accept DirectMemory into the Apache Incubator > [ ] +0 Don't care > [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... > > Thanks in advance for participating! > > All the best, have a nice day, > Simo > > P.S. Here's my +1 > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > = DirectMemory = > > == Abstract == > The following proposal is about Apache !DirectMemory, a Java > !OpenSource multi-layered cache implementation featuring off-heap > memory storage (a-la Terracotta !BigMemory) to enable caching of Java > objects without degrading JVM performance > > == Proposal == > !DirectMemory's main purpose is to to act as a second level cache > (after a heap based one) able to store large amounts of data without > filling up the Java heap and thus avoiding long garbage collection > cycles. Although serialization has a runtime cost store/retrieve > operations are in the sub-millisecond range being pretty acceptable in > every usage scenario even as a first level cache and, most of all, > outperforms heap storage when the count of the entries goes over a > certain amount. !DirectMemory implements cache eviction based on a > simple LFU (Least Frequently Used) algorythm and also on item > expiration. Included in the box is a small set of utility classes to > easily handle off-heap memory buffers. > > == Background == > !DirectMemory is a project was born in the 2010 thanks to Raffaele P. > Guidi initial effort under > [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already > licensed under the Apache License 2.0. > > == Rationale == > The rationale behind !DirectMemory is bringing off-heap caching to the > open source world, empowering FOSS developers and products with a tool > that enables breaking the heap barrier and override the JVM garbage > collection mechanism collection - which could be useful in scenarios > where RAM needs are over the usual limits (more than 8, 12, 24gb) and > to ease usage of off-heap memory in general > > = Current Status = > > == Meritocracy == > As a majority of the initial project members are existing ASF > committers, we recognize the desirability of running the project as a > meritocracy. We are eager to engage other members of the community > and operate to the standard of meritocracy that Apache emphasizes; we > believe this is the most effective method of growing our community and > enabling widespread adoption. > > == Core Developers == > In alphabetical order: > > * Christian Grobmeier > * Maurizio Cucchiara > * Olivier Lamy > * Raffaele P. Guidi > * Simone Gianni > * Simone Tripodi > * Tommaso Teofili > > == Alignment == > The purpose of the project is to develop and maintain !DirectMemory > implementation that can be used by other Apache projects. > > = Known Risks = > == Orphaned Products == > !DirectMemory does not have any reported production usage, yet, but is > getting traction with developers and being evaluated by potential > users and thus the risks of it being orphaned are minimal > > == Inexperience with Open Source == > All of the committers have experience working in one or more open > source projects inside and outside ASF. > > == Homogeneous Developers == > The list of initial committers are geographically distributed across > the Europe with no one company being associated with a majority of the > developers. Many of these initial developers are experienced Apache > committers already and all are experienced with working in distributed > development communities. > > == Reliance on Salaried Developers == > To the best of our knowledge, none of the initial committers are being > paid to develop code for this project. > > == Relationships with Other Apache Products == > !DirectMemory fits naturally in the ASF because it could be > successfully employed together with a large number of ASF products > ranging from JCS - as a new cache region between the heap and indexed > file ones, to ORM systems like Cayenne (i.e. replacing current OSCache > based implementation), Apache JDO and JPA implementations and also > java based databases (i.e. Derby) and all systems managing large > amounts of data from Hadoop to Cassandra > > == A Excessive Fascination with the Apache Brand == > While the Apache Software Foundation would be a good home for the > !DirectMemory project it already has some traction and it could live > on its own - however we see reciprocal benefits for both the ASF and > the project in adopting the brand to better reach the community > > = Documentation = > 1. [[https://github.com/raffaeleguidi/DirectMemory|The
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 (binding) On Sun, Oct 2, 2011 at 4:32 PM, Ralph Goers wrote: > +1 (binding) > > Ralph > > On Oct 2, 2011, at 12:36 AM, Simone Tripodi wrote: > >> Hi all guys, >> >> I'm now calling a formal VOTE on the DirectMemory proposal located here: >> >> http://wiki.apache.org/incubator/DirectMemoryProposal >> >> Proposal text copied at the bottom of this email. >> >> VOTE close on Tuesday, October 4, early 7:30 AM CET. >> >> Please VOTE: >> >> [ ] +1 Accept DirectMemory into the Apache Incubator >> [ ] +0 Don't care >> [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... >> >> Thanks in advance for participating! >> >> All the best, have a nice day, >> Simo >> >> P.S. Here's my +1 >> >> http://people.apache.org/~simonetripodi/ >> http://www.99soft.org/ >> >> = DirectMemory = >> >> == Abstract == >> The following proposal is about Apache !DirectMemory, a Java >> !OpenSource multi-layered cache implementation featuring off-heap >> memory storage (a-la Terracotta !BigMemory) to enable caching of Java >> objects without degrading JVM performance >> >> == Proposal == >> !DirectMemory's main purpose is to to act as a second level cache >> (after a heap based one) able to store large amounts of data without >> filling up the Java heap and thus avoiding long garbage collection >> cycles. Although serialization has a runtime cost store/retrieve >> operations are in the sub-millisecond range being pretty acceptable in >> every usage scenario even as a first level cache and, most of all, >> outperforms heap storage when the count of the entries goes over a >> certain amount. !DirectMemory implements cache eviction based on a >> simple LFU (Least Frequently Used) algorythm and also on item >> expiration. Included in the box is a small set of utility classes to >> easily handle off-heap memory buffers. >> >> == Background == >> !DirectMemory is a project was born in the 2010 thanks to Raffaele P. >> Guidi initial effort under >> [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already >> licensed under the Apache License 2.0. >> >> == Rationale == >> The rationale behind !DirectMemory is bringing off-heap caching to the >> open source world, empowering FOSS developers and products with a tool >> that enables breaking the heap barrier and override the JVM garbage >> collection mechanism collection - which could be useful in scenarios >> where RAM needs are over the usual limits (more than 8, 12, 24gb) and >> to ease usage of off-heap memory in general >> >> = Current Status = >> >> == Meritocracy == >> As a majority of the initial project members are existing ASF >> committers, we recognize the desirability of running the project as a >> meritocracy. We are eager to engage other members of the community >> and operate to the standard of meritocracy that Apache emphasizes; we >> believe this is the most effective method of growing our community and >> enabling widespread adoption. >> >> == Core Developers == >> In alphabetical order: >> >> * Christian Grobmeier >> * Maurizio Cucchiara >> * Olivier Lamy >> * Raffaele P. Guidi >> * Simone Gianni >> * Simone Tripodi >> * Tommaso Teofili >> >> == Alignment == >> The purpose of the project is to develop and maintain !DirectMemory >> implementation that can be used by other Apache projects. >> >> = Known Risks = >> == Orphaned Products == >> !DirectMemory does not have any reported production usage, yet, but is >> getting traction with developers and being evaluated by potential >> users and thus the risks of it being orphaned are minimal >> >> == Inexperience with Open Source == >> All of the committers have experience working in one or more open >> source projects inside and outside ASF. >> >> == Homogeneous Developers == >> The list of initial committers are geographically distributed across >> the Europe with no one company being associated with a majority of the >> developers. Many of these initial developers are experienced Apache >> committers already and all are experienced with working in distributed >> development communities. >> >> == Reliance on Salaried Developers == >> To the best of our knowledge, none of the initial committers are being >> paid to develop code for this project. >> >> == Relationships with Other Apache Products == >> !DirectMemory fits naturally in the ASF because it could be >> successfully employed together with a large number of ASF products >> ranging from JCS - as a new cache region between the heap and indexed >> file ones, to ORM systems like Cayenne (i.e. replacing current OSCache >> based implementation), Apache JDO and JPA implementations and also >> java based databases (i.e. Derby) and all systems managing large >> amounts of data from Hadoop to Cassandra >> >> == A Excessive Fascination with the Apache Brand == >> While the Apache Software Foundation would be a good home for the >> !DirectMemory project it already has some traction and it could live >> on its own - however we see reciprocal benefi
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
On Sun, Oct 2, 2011 at 9:36 AM, Simone Tripodi wrote: > [X] +1 Accept DirectMemory into the Apache Incubator (binding) /niklas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 (binding) Please VOTE: [X] +1 Accept DirectMemory into the Apache Incubator [ ] +0 Don't care [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... Sylvain -- Sylvain Wallez - http://bluxte.net - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 from me (binding). Good luck! Cheers, Chris On Oct 2, 2011, at 12:36 AM, Simone Tripodi wrote: > Hi all guys, > > I'm now calling a formal VOTE on the DirectMemory proposal located here: > > http://wiki.apache.org/incubator/DirectMemoryProposal > > Proposal text copied at the bottom of this email. > > VOTE close on Tuesday, October 4, early 7:30 AM CET. > > Please VOTE: > > [ ] +1 Accept DirectMemory into the Apache Incubator > [ ] +0 Don't care > [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... > > Thanks in advance for participating! > > All the best, have a nice day, > Simo > > P.S. Here's my +1 > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > = DirectMemory = > > == Abstract == > The following proposal is about Apache !DirectMemory, a Java > !OpenSource multi-layered cache implementation featuring off-heap > memory storage (a-la Terracotta !BigMemory) to enable caching of Java > objects without degrading JVM performance > > == Proposal == > !DirectMemory's main purpose is to to act as a second level cache > (after a heap based one) able to store large amounts of data without > filling up the Java heap and thus avoiding long garbage collection > cycles. Although serialization has a runtime cost store/retrieve > operations are in the sub-millisecond range being pretty acceptable in > every usage scenario even as a first level cache and, most of all, > outperforms heap storage when the count of the entries goes over a > certain amount. !DirectMemory implements cache eviction based on a > simple LFU (Least Frequently Used) algorythm and also on item > expiration. Included in the box is a small set of utility classes to > easily handle off-heap memory buffers. > > == Background == > !DirectMemory is a project was born in the 2010 thanks to Raffaele P. > Guidi initial effort under > [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already > licensed under the Apache License 2.0. > > == Rationale == > The rationale behind !DirectMemory is bringing off-heap caching to the > open source world, empowering FOSS developers and products with a tool > that enables breaking the heap barrier and override the JVM garbage > collection mechanism collection - which could be useful in scenarios > where RAM needs are over the usual limits (more than 8, 12, 24gb) and > to ease usage of off-heap memory in general > > = Current Status = > > == Meritocracy == > As a majority of the initial project members are existing ASF > committers, we recognize the desirability of running the project as a > meritocracy. We are eager to engage other members of the community > and operate to the standard of meritocracy that Apache emphasizes; we > believe this is the most effective method of growing our community and > enabling widespread adoption. > > == Core Developers == > In alphabetical order: > > * Christian Grobmeier > * Maurizio Cucchiara > * Olivier Lamy > * Raffaele P. Guidi > * Simone Gianni > * Simone Tripodi > * Tommaso Teofili > > == Alignment == > The purpose of the project is to develop and maintain !DirectMemory > implementation that can be used by other Apache projects. > > = Known Risks = > == Orphaned Products == > !DirectMemory does not have any reported production usage, yet, but is > getting traction with developers and being evaluated by potential > users and thus the risks of it being orphaned are minimal > > == Inexperience with Open Source == > All of the committers have experience working in one or more open > source projects inside and outside ASF. > > == Homogeneous Developers == > The list of initial committers are geographically distributed across > the Europe with no one company being associated with a majority of the > developers. Many of these initial developers are experienced Apache > committers already and all are experienced with working in distributed > development communities. > > == Reliance on Salaried Developers == > To the best of our knowledge, none of the initial committers are being > paid to develop code for this project. > > == Relationships with Other Apache Products == > !DirectMemory fits naturally in the ASF because it could be > successfully employed together with a large number of ASF products > ranging from JCS - as a new cache region between the heap and indexed > file ones, to ORM systems like Cayenne (i.e. replacing current OSCache > based implementation), Apache JDO and JPA implementations and also > java based databases (i.e. Derby) and all systems managing large > amounts of data from Hadoop to Cassandra > > == A Excessive Fascination with the Apache Brand == > While the Apache Software Foundation would be a good home for the > !DirectMemory project it already has some traction and it could live > on its own - however we see reciprocal benefits for both the ASF and > the project in adopting the brand to better reach the community > > = Documentation = > 1. [[https://github.com/r
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 (non binding) Simone 2011/10/2 Mattmann, Chris A (388J) > +1 from me (binding). > > Good luck! > > Cheers, > Chris > > On Oct 2, 2011, at 12:36 AM, Simone Tripodi wrote: > > > Hi all guys, > > > > I'm now calling a formal VOTE on the DirectMemory proposal located here: > > > > http://wiki.apache.org/incubator/DirectMemoryProposal > > > > Proposal text copied at the bottom of this email. > > > > VOTE close on Tuesday, October 4, early 7:30 AM CET. > > > > Please VOTE: > > > > [ ] +1 Accept DirectMemory into the Apache Incubator > > [ ] +0 Don't care > > [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... > > > > Thanks in advance for participating! > > > > All the best, have a nice day, > > Simo > > > > P.S. Here's my +1 > > > > http://people.apache.org/~simonetripodi/ > > http://www.99soft.org/ > > > > = DirectMemory = > > > > == Abstract == > > The following proposal is about Apache !DirectMemory, a Java > > !OpenSource multi-layered cache implementation featuring off-heap > > memory storage (a-la Terracotta !BigMemory) to enable caching of Java > > objects without degrading JVM performance > > > > == Proposal == > > !DirectMemory's main purpose is to to act as a second level cache > > (after a heap based one) able to store large amounts of data without > > filling up the Java heap and thus avoiding long garbage collection > > cycles. Although serialization has a runtime cost store/retrieve > > operations are in the sub-millisecond range being pretty acceptable in > > every usage scenario even as a first level cache and, most of all, > > outperforms heap storage when the count of the entries goes over a > > certain amount. !DirectMemory implements cache eviction based on a > > simple LFU (Least Frequently Used) algorythm and also on item > > expiration. Included in the box is a small set of utility classes to > > easily handle off-heap memory buffers. > > > > == Background == > > !DirectMemory is a project was born in the 2010 thanks to Raffaele P. > > Guidi initial effort under > > [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already > > licensed under the Apache License 2.0. > > > > == Rationale == > > The rationale behind !DirectMemory is bringing off-heap caching to the > > open source world, empowering FOSS developers and products with a tool > > that enables breaking the heap barrier and override the JVM garbage > > collection mechanism collection - which could be useful in scenarios > > where RAM needs are over the usual limits (more than 8, 12, 24gb) and > > to ease usage of off-heap memory in general > > > > = Current Status = > > > > == Meritocracy == > > As a majority of the initial project members are existing ASF > > committers, we recognize the desirability of running the project as a > > meritocracy. We are eager to engage other members of the community > > and operate to the standard of meritocracy that Apache emphasizes; we > > believe this is the most effective method of growing our community and > > enabling widespread adoption. > > > > == Core Developers == > > In alphabetical order: > > > > * Christian Grobmeier > > * Maurizio Cucchiara > > * Olivier Lamy > > * Raffaele P. Guidi > > * Simone Gianni > > * Simone Tripodi > > * Tommaso Teofili > > > > == Alignment == > > The purpose of the project is to develop and maintain !DirectMemory > > implementation that can be used by other Apache projects. > > > > = Known Risks = > > == Orphaned Products == > > !DirectMemory does not have any reported production usage, yet, but is > > getting traction with developers and being evaluated by potential > > users and thus the risks of it being orphaned are minimal > > > > == Inexperience with Open Source == > > All of the committers have experience working in one or more open > > source projects inside and outside ASF. > > > > == Homogeneous Developers == > > The list of initial committers are geographically distributed across > > the Europe with no one company being associated with a majority of the > > developers. Many of these initial developers are experienced Apache > > committers already and all are experienced with working in distributed > > development communities. > > > > == Reliance on Salaried Developers == > > To the best of our knowledge, none of the initial committers are being > > paid to develop code for this project. > > > > == Relationships with Other Apache Products == > > !DirectMemory fits naturally in the ASF because it could be > > successfully employed together with a large number of ASF products > > ranging from JCS - as a new cache region between the heap and indexed > > file ones, to ORM systems like Cayenne (i.e. replacing current OSCache > > based implementation), Apache JDO and JPA implementations and also > > java based databases (i.e. Derby) and all systems managing large > > amounts of data from Hadoop to Cassandra > > > > == A Excessive Fascination with the Apache Brand == > > While the Apache Software Foundation
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 (binding) -- Olivier Le 2 oct. 2011 09:36, "Simone Tripodi" a écrit : > Hi all guys, > > I'm now calling a formal VOTE on the DirectMemory proposal located here: > > http://wiki.apache.org/incubator/DirectMemoryProposal > > Proposal text copied at the bottom of this email. > > VOTE close on Tuesday, October 4, early 7:30 AM CET. > > Please VOTE: > > [ ] +1 Accept DirectMemory into the Apache Incubator > [ ] +0 Don't care > [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... > > Thanks in advance for participating! > > All the best, have a nice day, > Simo > > P.S. Here's my +1 > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > = DirectMemory = > > == Abstract == > The following proposal is about Apache !DirectMemory, a Java > !OpenSource multi-layered cache implementation featuring off-heap > memory storage (a-la Terracotta !BigMemory) to enable caching of Java > objects without degrading JVM performance > > == Proposal == > !DirectMemory's main purpose is to to act as a second level cache > (after a heap based one) able to store large amounts of data without > filling up the Java heap and thus avoiding long garbage collection > cycles. Although serialization has a runtime cost store/retrieve > operations are in the sub-millisecond range being pretty acceptable in > every usage scenario even as a first level cache and, most of all, > outperforms heap storage when the count of the entries goes over a > certain amount. !DirectMemory implements cache eviction based on a > simple LFU (Least Frequently Used) algorythm and also on item > expiration. Included in the box is a small set of utility classes to > easily handle off-heap memory buffers. > > == Background == > !DirectMemory is a project was born in the 2010 thanks to Raffaele P. > Guidi initial effort under > [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already > licensed under the Apache License 2.0. > > == Rationale == > The rationale behind !DirectMemory is bringing off-heap caching to the > open source world, empowering FOSS developers and products with a tool > that enables breaking the heap barrier and override the JVM garbage > collection mechanism collection - which could be useful in scenarios > where RAM needs are over the usual limits (more than 8, 12, 24gb) and > to ease usage of off-heap memory in general > > = Current Status = > > == Meritocracy == > As a majority of the initial project members are existing ASF > committers, we recognize the desirability of running the project as a > meritocracy. We are eager to engage other members of the community > and operate to the standard of meritocracy that Apache emphasizes; we > believe this is the most effective method of growing our community and > enabling widespread adoption. > > == Core Developers == > In alphabetical order: > > * Christian Grobmeier > * Maurizio Cucchiara > * Olivier Lamy > * Raffaele P. Guidi > * Simone Gianni > * Simone Tripodi > * Tommaso Teofili > > == Alignment == > The purpose of the project is to develop and maintain !DirectMemory > implementation that can be used by other Apache projects. > > = Known Risks = > == Orphaned Products == > !DirectMemory does not have any reported production usage, yet, but is > getting traction with developers and being evaluated by potential > users and thus the risks of it being orphaned are minimal > > == Inexperience with Open Source == > All of the committers have experience working in one or more open > source projects inside and outside ASF. > > == Homogeneous Developers == > The list of initial committers are geographically distributed across > the Europe with no one company being associated with a majority of the > developers. Many of these initial developers are experienced Apache > committers already and all are experienced with working in distributed > development communities. > > == Reliance on Salaried Developers == > To the best of our knowledge, none of the initial committers are being > paid to develop code for this project. > > == Relationships with Other Apache Products == > !DirectMemory fits naturally in the ASF because it could be > successfully employed together with a large number of ASF products > ranging from JCS - as a new cache region between the heap and indexed > file ones, to ORM systems like Cayenne (i.e. replacing current OSCache > based implementation), Apache JDO and JPA implementations and also > java based databases (i.e. Derby) and all systems managing large > amounts of data from Hadoop to Cassandra > > == A Excessive Fascination with the Apache Brand == > While the Apache Software Foundation would be a good home for the > !DirectMemory project it already has some traction and it could live > on its own - however we see reciprocal benefits for both the ASF and > the project in adopting the brand to better reach the community > > = Documentation = > 1. [[https://github.com/raffaeleguidi/DirectMemory|The original > DirectMemory Hom
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
Very interesting project. +1 (non-binding). Thanks, +Vinod On Sun, Oct 2, 2011 at 1:06 PM, Simone Tripodi wrote: > Hi all guys, > > I'm now calling a formal VOTE on the DirectMemory proposal located here: > > http://wiki.apache.org/incubator/DirectMemoryProposal > > Proposal text copied at the bottom of this email. > > VOTE close on Tuesday, October 4, early 7:30 AM CET. > > Please VOTE: > > [ ] +1 Accept DirectMemory into the Apache Incubator > [ ] +0 Don't care > [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... > > Thanks in advance for participating! > > All the best, have a nice day, > Simo > > P.S. Here's my +1 > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > = DirectMemory = > > == Abstract == > The following proposal is about Apache !DirectMemory, a Java > !OpenSource multi-layered cache implementation featuring off-heap > memory storage (a-la Terracotta !BigMemory) to enable caching of Java > objects without degrading JVM performance > > == Proposal == > !DirectMemory's main purpose is to to act as a second level cache > (after a heap based one) able to store large amounts of data without > filling up the Java heap and thus avoiding long garbage collection > cycles. Although serialization has a runtime cost store/retrieve > operations are in the sub-millisecond range being pretty acceptable in > every usage scenario even as a first level cache and, most of all, > outperforms heap storage when the count of the entries goes over a > certain amount. !DirectMemory implements cache eviction based on a > simple LFU (Least Frequently Used) algorythm and also on item > expiration. Included in the box is a small set of utility classes to > easily handle off-heap memory buffers. > > == Background == > !DirectMemory is a project was born in the 2010 thanks to Raffaele P. > Guidi initial effort under > [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already > licensed under the Apache License 2.0. > > == Rationale == > The rationale behind !DirectMemory is bringing off-heap caching to the > open source world, empowering FOSS developers and products with a tool > that enables breaking the heap barrier and override the JVM garbage > collection mechanism collection - which could be useful in scenarios > where RAM needs are over the usual limits (more than 8, 12, 24gb) and > to ease usage of off-heap memory in general > > = Current Status = > > == Meritocracy == > As a majority of the initial project members are existing ASF > committers, we recognize the desirability of running the project as a > meritocracy. We are eager to engage other members of the community > and operate to the standard of meritocracy that Apache emphasizes; we > believe this is the most effective method of growing our community and > enabling widespread adoption. > > == Core Developers == > In alphabetical order: > > * Christian Grobmeier > * Maurizio Cucchiara > * Olivier Lamy > * Raffaele P. Guidi > * Simone Gianni > * Simone Tripodi > * Tommaso Teofili > > == Alignment == > The purpose of the project is to develop and maintain !DirectMemory > implementation that can be used by other Apache projects. > > = Known Risks = > == Orphaned Products == > !DirectMemory does not have any reported production usage, yet, but is > getting traction with developers and being evaluated by potential > users and thus the risks of it being orphaned are minimal > > == Inexperience with Open Source == > All of the committers have experience working in one or more open > source projects inside and outside ASF. > > == Homogeneous Developers == > The list of initial committers are geographically distributed across > the Europe with no one company being associated with a majority of the > developers. Many of these initial developers are experienced Apache > committers already and all are experienced with working in distributed > development communities. > > == Reliance on Salaried Developers == > To the best of our knowledge, none of the initial committers are being > paid to develop code for this project. > > == Relationships with Other Apache Products == > !DirectMemory fits naturally in the ASF because it could be > successfully employed together with a large number of ASF products > ranging from JCS - as a new cache region between the heap and indexed > file ones, to ORM systems like Cayenne (i.e. replacing current OSCache > based implementation), Apache JDO and JPA implementations and also > java based databases (i.e. Derby) and all systems managing large > amounts of data from Hadoop to Cassandra > > == A Excessive Fascination with the Apache Brand == > While the Apache Software Foundation would be a good home for the > !DirectMemory project it already has some traction and it could live > on its own - however we see reciprocal benefits for both the ASF and > the project in adopting the brand to better reach the community > > = Documentation = > 1. [[https://github.com/raff
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 (binding) Tommaso 2011/10/2 Simone Tripodi > Hi all guys, > > I'm now calling a formal VOTE on the DirectMemory proposal located here: > > http://wiki.apache.org/incubator/DirectMemoryProposal > > Proposal text copied at the bottom of this email. > > VOTE close on Tuesday, October 4, early 7:30 AM CET. > > Please VOTE: > > [ ] +1 Accept DirectMemory into the Apache Incubator > [ ] +0 Don't care > [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... > > Thanks in advance for participating! > > All the best, have a nice day, > Simo > > P.S. Here's my +1 > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > = DirectMemory = > > == Abstract == > The following proposal is about Apache !DirectMemory, a Java > !OpenSource multi-layered cache implementation featuring off-heap > memory storage (a-la Terracotta !BigMemory) to enable caching of Java > objects without degrading JVM performance > > == Proposal == > !DirectMemory's main purpose is to to act as a second level cache > (after a heap based one) able to store large amounts of data without > filling up the Java heap and thus avoiding long garbage collection > cycles. Although serialization has a runtime cost store/retrieve > operations are in the sub-millisecond range being pretty acceptable in > every usage scenario even as a first level cache and, most of all, > outperforms heap storage when the count of the entries goes over a > certain amount. !DirectMemory implements cache eviction based on a > simple LFU (Least Frequently Used) algorythm and also on item > expiration. Included in the box is a small set of utility classes to > easily handle off-heap memory buffers. > > == Background == > !DirectMemory is a project was born in the 2010 thanks to Raffaele P. > Guidi initial effort under > [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already > licensed under the Apache License 2.0. > > == Rationale == > The rationale behind !DirectMemory is bringing off-heap caching to the > open source world, empowering FOSS developers and products with a tool > that enables breaking the heap barrier and override the JVM garbage > collection mechanism collection - which could be useful in scenarios > where RAM needs are over the usual limits (more than 8, 12, 24gb) and > to ease usage of off-heap memory in general > > = Current Status = > > == Meritocracy == > As a majority of the initial project members are existing ASF > committers, we recognize the desirability of running the project as a > meritocracy. We are eager to engage other members of the community > and operate to the standard of meritocracy that Apache emphasizes; we > believe this is the most effective method of growing our community and > enabling widespread adoption. > > == Core Developers == > In alphabetical order: > > * Christian Grobmeier > * Maurizio Cucchiara > * Olivier Lamy > * Raffaele P. Guidi > * Simone Gianni > * Simone Tripodi > * Tommaso Teofili > > == Alignment == > The purpose of the project is to develop and maintain !DirectMemory > implementation that can be used by other Apache projects. > > = Known Risks = > == Orphaned Products == > !DirectMemory does not have any reported production usage, yet, but is > getting traction with developers and being evaluated by potential > users and thus the risks of it being orphaned are minimal > > == Inexperience with Open Source == > All of the committers have experience working in one or more open > source projects inside and outside ASF. > > == Homogeneous Developers == > The list of initial committers are geographically distributed across > the Europe with no one company being associated with a majority of the > developers. Many of these initial developers are experienced Apache > committers already and all are experienced with working in distributed > development communities. > > == Reliance on Salaried Developers == > To the best of our knowledge, none of the initial committers are being > paid to develop code for this project. > > == Relationships with Other Apache Products == > !DirectMemory fits naturally in the ASF because it could be > successfully employed together with a large number of ASF products > ranging from JCS - as a new cache region between the heap and indexed > file ones, to ORM systems like Cayenne (i.e. replacing current OSCache > based implementation), Apache JDO and JPA implementations and also > java based databases (i.e. Derby) and all systems managing large > amounts of data from Hadoop to Cassandra > > == A Excessive Fascination with the Apache Brand == > While the Apache Software Foundation would be a good home for the > !DirectMemory project it already has some traction and it could live > on its own - however we see reciprocal benefits for both the ASF and > the project in adopting the brand to better reach the community > > = Documentation = > 1. [[https://github.com/raffaeleguidi/DirectMemory|The original > DirectMemory HomePage]] > 2. [
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 ...ant On Sun, Oct 2, 2011 at 8:36 AM, Simone Tripodi wrote: > Hi all guys, > > I'm now calling a formal VOTE on the DirectMemory proposal located here: > > http://wiki.apache.org/incubator/DirectMemoryProposal > > Proposal text copied at the bottom of this email. > > VOTE close on Tuesday, October 4, early 7:30 AM CET. > > Please VOTE: > > [ ] +1 Accept DirectMemory into the Apache Incubator > [ ] +0 Don't care > [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... > > Thanks in advance for participating! > > All the best, have a nice day, > Simo > > P.S. Here's my +1 > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > = DirectMemory = > > == Abstract == > The following proposal is about Apache !DirectMemory, a Java > !OpenSource multi-layered cache implementation featuring off-heap > memory storage (a-la Terracotta !BigMemory) to enable caching of Java > objects without degrading JVM performance > > == Proposal == > !DirectMemory's main purpose is to to act as a second level cache > (after a heap based one) able to store large amounts of data without > filling up the Java heap and thus avoiding long garbage collection > cycles. Although serialization has a runtime cost store/retrieve > operations are in the sub-millisecond range being pretty acceptable in > every usage scenario even as a first level cache and, most of all, > outperforms heap storage when the count of the entries goes over a > certain amount. !DirectMemory implements cache eviction based on a > simple LFU (Least Frequently Used) algorythm and also on item > expiration. Included in the box is a small set of utility classes to > easily handle off-heap memory buffers. > > == Background == > !DirectMemory is a project was born in the 2010 thanks to Raffaele P. > Guidi initial effort under > [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already > licensed under the Apache License 2.0. > > == Rationale == > The rationale behind !DirectMemory is bringing off-heap caching to the > open source world, empowering FOSS developers and products with a tool > that enables breaking the heap barrier and override the JVM garbage > collection mechanism collection - which could be useful in scenarios > where RAM needs are over the usual limits (more than 8, 12, 24gb) and > to ease usage of off-heap memory in general > > = Current Status = > > == Meritocracy == > As a majority of the initial project members are existing ASF > committers, we recognize the desirability of running the project as a > meritocracy. We are eager to engage other members of the community > and operate to the standard of meritocracy that Apache emphasizes; we > believe this is the most effective method of growing our community and > enabling widespread adoption. > > == Core Developers == > In alphabetical order: > > * Christian Grobmeier > * Maurizio Cucchiara > * Olivier Lamy > * Raffaele P. Guidi > * Simone Gianni > * Simone Tripodi > * Tommaso Teofili > > == Alignment == > The purpose of the project is to develop and maintain !DirectMemory > implementation that can be used by other Apache projects. > > = Known Risks = > == Orphaned Products == > !DirectMemory does not have any reported production usage, yet, but is > getting traction with developers and being evaluated by potential > users and thus the risks of it being orphaned are minimal > > == Inexperience with Open Source == > All of the committers have experience working in one or more open > source projects inside and outside ASF. > > == Homogeneous Developers == > The list of initial committers are geographically distributed across > the Europe with no one company being associated with a majority of the > developers. Many of these initial developers are experienced Apache > committers already and all are experienced with working in distributed > development communities. > > == Reliance on Salaried Developers == > To the best of our knowledge, none of the initial committers are being > paid to develop code for this project. > > == Relationships with Other Apache Products == > !DirectMemory fits naturally in the ASF because it could be > successfully employed together with a large number of ASF products > ranging from JCS - as a new cache region between the heap and indexed > file ones, to ORM systems like Cayenne (i.e. replacing current OSCache > based implementation), Apache JDO and JPA implementations and also > java based databases (i.e. Derby) and all systems managing large > amounts of data from Hadoop to Cassandra > > == A Excessive Fascination with the Apache Brand == > While the Apache Software Foundation would be a good home for the > !DirectMemory project it already has some traction and it could live > on its own - however we see reciprocal benefits for both the ASF and > the project in adopting the brand to better reach the community > > = Documentation = > 1. [[https://github.com/raffaeleguidi/DirectMemory|The original > DirectMemo
