具有开创性的“农村能源发展项目”照亮了160多万人的生活——并获得了2008年度“阿什登可再生能源奖”。玛莉安·贝德特此撰文。
在遥远的中国西部和西北部,半游牧民冬夜蜷缩在他们偏僻的住宅里,夏天住在帐篷里,煤油灯、酥油灯和蜡烛冒着烟,在昏暗的灯光下,视线模糊。这些传统的牧民是这个国家最贫困人口的一部分,现金收入极少,以物易物,需要用钱时卖一头牦牛或者一头羊。
这一区域分布在九个省,很多地方气候非常寒冷,地势很高,有的地方海拔高达4,000米。在青海省,牧民冬季在相对防寒的山谷中放牧,夏季则迁移到海拔更高的牧场。在同样遥远和人口稀少的农业区,例如内蒙古、甘肃和四川等地,情形也大致相同,生活条件艰苦。通常,农村居民和最近的邻居相距遥远,获得的商品和服务有限——特别是奢侈的电网供电。
不过,近年来情况正在逐渐好转。
由于中国的“农村能源发展项目”(REDP),居民能够买得起的高质量太阳能照明设备在这个地区越来越多。这个2001年由国家发改委和世界银行联合发起、得到全球环境基金国际赠款的中国项目,在2008年6月获得了近4万美元的“阿什登可持续能源奖”。
从项目启动到今年年中,通过一个有补贴的项目,中国北部和西北部地区的偏远、无电家庭安装了402,000光伏(PV)的太阳能户用系统。这些太阳能户用光伏系统是独立的电力设备,使用光伏组件提供电力。一个典型的太阳能户用系统装在一个金属手提箱里,便于携带,能够为两盏电灯提供电力,并为手机充电。(收放机、电视机和影碟机可以连接到更大的系统。)
REDP技术进步经理罗欣莲称,按照平均每户四口人计算,目前该系统已使161万人受益,“特别是在西藏”。她接着表示,这些系统给用户带来了新的机会,提高了他们的家庭生活质量。
使用太阳能嵌板的牧民帐篷
阿什登奖创始人兼主席巴特勒-斯洛斯表示,“这是一个极其重要的项目”,它“扶持了中国光伏产业的快速发展,在保持低成本的同时,改善了产品的质量,大大地扩大了太阳能户用系统市场,支持了供应商、批发商和零售商网络的发展。”
明亮、高质量的电灯好处多多,成年人晚上在家可以做更多的事情,学生则可以每天学习更长的时间。蜡烛、煤油灯和酥油灯,除了昏暗和冒烟之外,还很容易被打翻,带来重大的火灾隐患。REDP称,照明系统使得村里晚上可以有更多的活动,有助于加强邻里关系。
在一些地区安装了更大的太阳能系统,为学校、诊所、路边商店餐馆以及寺庙和各类院校供电照明,同时还以为村庄卫星电话、洪水预警系统、气候监测站和其他公共服务提供电力。(受益于该项目的一所学校校长说:“有太阳能意味着天黑时不必停课。”与此同时,由于有了便携式电力系统,一位放牦牛的牧民表示“当我们前往夏季牧场时”醉心于听音乐。)
世界银行对中国四个县的一项调查显示,太阳能户用系统能源输出的58%被用于照明,约38%用于放收音机,这一连接外部世界的重要纽带为人们提供了学习和娱乐机会,并带来了更大的安全感(尤其是在夏季牧场)。其它设备——例如录音机、影碟机和电视机——约占能源使用的4%。(然而,电话充电功能并不总是有用;在更偏远的地区,通信网络只为聚居的村庄提供服务。)
此外,太阳能户用系统对环境也有好处,即使环境足迹在这些地区还非常小:相对于不可再生的煤油和蜡烛冒烟造成家庭污染,使用可再生的太阳能可以减少温室气体。REDP建立了一个拥有约80个太阳能户用系统地方零售商和32个批发商的网络,创造了大约1,500个固定工作和3,000个临时工作。随着项目的扩大,在产品质量、服务和管理上,制定了越来越严格的标准。
罗欣莲表示:“我们完成了所有的既定目标。”2008年6月底——带着阿什登奖——REDP项目圆满结束了。但这并非故事的结局,REDP开始发展为“中国光伏行业协会”,将继续——并跨越——原有项目的工作。新的组织将提供顾问服务,设立一个企业对企业的网站,以及每两年提供一份关于中国光伏产业的报告。
销售现在已没有补贴,因为光伏的好处广为人知,而且系统可靠,价格不贵。当地人清楚地看到了好处,而且想要安装这种系统。一些家庭升级到更大的系统,甚至安装两套系统——为更多的房间和更长的时间提供照明,或者为电视机等更多的电器提供电力。农民可以在地方市场销售农产品,并把新买的太阳能光伏组件用驴车带回家。
REDP提供的系统采用10-500峰瓦(Wp)的光伏容量,由一个光伏组件、一块电池、一个充电控制器(调节器)组成,有时还有一个逆变器,加上灯泡和一个直流电插座,用于插收音机或者手机充电器。户用系统目前具有11.1兆瓦的总峰值容量,每个系统平均为28峰瓦。太阳能户用系统2007年的平均售价为1,221元(约175美元)——与一头牦牛的价钱差不多。
买主通常按零售价一次性全价付款,不过在某些地区,地方政府采用赠送的方式来帮助购买,而且零售商之间相互竞争,可能提供信贷或者价格优惠。REDP称,在少数情况下,政府批量购买系统,并免费或者半价发放。
光伏组件占整个系统成本的50%左右。因为组件成本低,而且是在中国生产,太阳能户用系统的零售价按国际标准来看并不贵。不过,随着对零售商补贴的停止,价格预计将提高20%左右。经销商能够进行基本的维修和更换,他们表示,系统是可靠的。当他们排除故障时,主要问题是短路和电器超载造成的。
组件有10年的质保,但预计将有两倍于此的使用寿命。其他的部件也提供质保:充电控制器两年,电池、逆变器和电灯一年。印有中文和当地语言的说明书上画有简单的图示,即使不识字也能看懂系统是如何工作的。(在表示光伏组件易脆的警示图上,一头牦牛在用头撞一个太阳能电池板,上面打着一个红色的“X”。)
鉴于中国可再生能源装机容量计划到2020年实现翻番,REDP看到了扩大太阳能户用系统市场的巨大机会。根据在未来12年里实现3亿峰瓦的农村光伏能源目标——包括离网和并网光伏,罗欣莲表示:“太阳能光伏是农村电气化的关键。”
除了“为众多的人口提供可持续能源以满足他们的需求外”,阿什登奖主席巴特勒-斯洛斯表示,“这一模式正在被中国其他的几个捐赠项目所采用。”REDP光伏项目经理王卫表示,实际上,世界银行正鼓励菲律宾、蒙古、斯里兰卡和玻利维亚等其他发展中国家发展类似的系统。
巴特勒-斯洛斯指出,在一个“20亿人仍然无法获得现代能源的世界,燃料价格逐步上升,气候变化的影响日益明显”,像REDP这样的开创性能源项目指明了“实际而明智的前进之路”。通过利用可再生的水能、风能和太阳能,“这些项目为节省能源而采取容易实现的措施作出了示范,让我们看到了未来。”
即使是对那些在中国偏远山区和夏季牧场的游牧民和他们的牦牛而言。
玛莉安·贝德:“中外对话”副主编
One of our customers was setting up box for MySQL LVM backups. The box had 2 RAID volumes (internal drives and enclosure) with database being stored on enclosure drives and internal drives used pretty much for OS and logs (database grew too large and so was moved to enclosure completely).
As database was large and active I thought it would make sense to have LVM undo space located on the internal drives so LVM and backup has less backup on the running system.
As the system was configured creating snapshot volume with 100G of undo space failed complaining there is not enough space available on the volume….
The problem was internal and external volumes were configured as different “volume groups”. Volume groups in LVM live completely isolated life and you can’t use space from one volume group for snapshot for another.
What should have done instead is creating single volume group and having RAID volumes as physical volumes.
If you also have done such mistake there is vgmerge command which allows to merge volume groups together without data loss. (Though I took backup anyway just to be on the safe side)
P.S That would be interested to benchmark one day how LVM performs in shapshot mode in case undo space is stored on the same device vs different device.
Entry posted by peter | 3 comments
by Matt Matyas, Google Sales Engineer
Recently the API team got together to think about ways you can get the most out the AdWords API. If you're new to the AdWords API, or even a longtime user, we hope you’ll find these tips useful.
1) Stay in touch
Want to know about the newest releases, options, and features in the AdWords API? Check out the following resources, where you can hear from us and interact with other developers:
2) Keep current with versioning
Through our versioning, we're continually offering added functionality to the AdWords API, as well as making changes to its existing functionality. Migrate your code to newer versions, and you can take advantage of the latest features. In addition, staying up-to-date with the versioning via our website or mailing list is a great way to make sure your functionality won't unexpectedly go dark as we sunset old versions. When sunsetting any version of the AdWords API, we give months of advance notice so you have plenty of time to upgrade.
3) Manage your API Units
The AdWords API uses an API Units System to distribute our resources fairly among our many users and ensure reliability for all. Understanding your AdWords API Units usage over time via the following resources will allow you to budget according to your needs:
Another best practice in API Unit management is to analyze your expected AdWords API usage and forecast expected unit implications. Our rate sheet tells how many API Units are consumed per operation. By inspecting historical usage patterns and estimating API Unit implications for future AdWords API projects you may employ, you can accomplish your goals while working within your API Unit allocations.
4) Test in the sandbox
Want a place to test without consuming API units? Use the AdWords API Sandbox environment to test out your applications without consuming API Units. The sandbox replicates the API of the live site so you can test and debug new code, allowing you to develop solid applications without any risk of harming live data.
5) Use reports
How do you gauge how your campaigns are doing? Reporting can give you all of the essential statistics you need, with minimal API Unit costs. Reporting can help you conveniently analyze many aspects of your campaigns, from structure to performance. Some examples:
6) Insert ads before keywords
Optimize your campaigns by always inserting ads into an ad group before placing keywords in it. Unlike creating ad groups through adwords.google.com or AdWords Editor, if you insert keywords first when you create an ad group via AdWords API, AdWords' Quality Based Bidding will temporarily assign relatively high minimum cost-per-click values. This is a very common mistake, and one that can very easily be avoided. Take extra care to follow this tip to ensure optimal performance.
7) Create a local store of AdWords data
Enjoy the power of having AdWords data on a server in your office. Many users boost the efficiency of their AdWords API response times by mirroring important parts of their campaigns in a local database. Having a copy of the data allows you to rapidly query against it and retrieve information on your campaigns, ad groups, keywords, and more without having to wait for a SOAP request to travel across the internet and be processed and returned. This setup can also eliminate waste if you need to make redundant AdWords API requests.
One word of caution: it's crucial to keep your local data updated, otherwise it can quickly become stale. This is especially true since it's possible to update AdWords data via multiple channels (i.e., adwords.google.com, the AdWords Editor, the AdWords API, and even other systems), meaning you could fall out of sync if you’re not diligent.
8) Use the AdWords API libraries
Why reinvent the AdWords API wheel? We’ve created two resources to help jump-start your development.
9) Optimize your account
Use the AdWords API to streamline the performance of your campaigns and eliminate waste.
10) Handle disapproved ads
Sometimes ads submitted to AdWords don't comply with our editorial or content guidelines, which are designed to create as user-friendly experience as possible. To handle any disapprovals smoothly and reduce overall ad downtime, design a process for handling disapproved ads.
七月 2008 | ||||||
一 | 二 | 三 | 四 | 五 | 六 | 日 |
1 | 2 | 3 | 4 | 5 | 6 | |
7 | 8 | 9 | 10 | 11 | 12 | 13 |
14 | 15 | 16 | 17 | 18 | 19 | 20 |
21 | 22 | 23 | 24 | 25 | 26 | 27 |
28 | 29 | 30 | 31 |