Re: [Gelato-technical] Re: Serious performance degradation on a RAID with kernel 2.6.10-bk7 and later
Luck, Tony wrote: Only a new user would have to pull the whole history ... and for most uses it is sufficient to just pull the current top of the tree. Linus' own tree only has a history going back to 2.6.12.-rc2 (when he started using git). Someday there might be a server daemon that can batch up the changes for a "pull" to conserve network bandwidth. There is a mailing list "git@vger.kernel.org" where these issues are discussed. Archives are available at marc.theaimsgroup.com and gelato. Thanks tony I wasn't aware of the list, I'll look there for git info from now on. Best Regards, Stan -Tony - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Gelato-technical] Re: Serious performance degradation on a RAID with kernel 2.6.10-bk7 and later
Luck, Tony wrote: Yeah, I'm facing the same issue. I started playing with git last night. Apart from disk-space usage, it's very nice, though I really hope someone puts together a web-interface on top of git soon so we can seek what changed when and by whom. Disk space issues? A complete git repository of the Linux kernel with all changesets back to 2.4.0 takes just over 3G ... which is big compared to BK, but 3G of disk only costs about $1 (for IDE ... if you want 15K rpm SCSI, then you'll pay a lot more). Network bandwidth is likely to be a bigger problem. That said, is there any plan to change how this functions in the future to solve these problems? I.e. have it not use so much diskspace and thus use less bandwith. Am I misunderstanding in assuming that after say 1000 commits go into the tree it could end up several megs or gigs bigger? If that is the case might it not be more prudent to sort this out now? There's a prototype web i/f at http://grmso.net:8090/ that's already looking fairly slick. Yes it is very slick. Kudos to the creator. -sb -Tony - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Gelato-technical] Re: Serious performance degradation on a RAID with kernel 2.6.10-bk7 and later
Luck, Tony wrote: Yeah, I'm facing the same issue. I started playing with git last night. Apart from disk-space usage, it's very nice, though I really hope someone puts together a web-interface on top of git soon so we can seek what changed when and by whom. Disk space issues? A complete git repository of the Linux kernel with all changesets back to 2.4.0 takes just over 3G ... which is big compared to BK, but 3G of disk only costs about $1 (for IDE ... if you want 15K rpm SCSI, then you'll pay a lot more). Network bandwidth is likely to be a bigger problem. That said, is there any plan to change how this functions in the future to solve these problems? I.e. have it not use so much diskspace and thus use less bandwith. Am I misunderstanding in assuming that after say 1000 commits go into the tree it could end up several megs or gigs bigger? If that is the case might it not be more prudent to sort this out now? There's a prototype web i/f at http://grmso.net:8090/ that's already looking fairly slick. Yes it is very slick. Kudos to the creator. -sb -Tony - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Gelato-technical] Re: Serious performance degradation on a RAID with kernel 2.6.10-bk7 and later
Luck, Tony wrote: SNIP Only a new user would have to pull the whole history ... and for most uses it is sufficient to just pull the current top of the tree. Linus' own tree only has a history going back to 2.6.12.-rc2 (when he started using git). Someday there might be a server daemon that can batch up the changes for a pull to conserve network bandwidth. There is a mailing list git@vger.kernel.org where these issues are discussed. Archives are available at marc.theaimsgroup.com and gelato. Thanks tony I wasn't aware of the list, I'll look there for git info from now on. Best Regards, Stan -Tony - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
