wiki.met.no wdb:developers

Building in Debian

anonymous@undisclosed.example.com (Anonymous) — Tue, 31 May 2022 09:29:32 +0000

Building in Debian Compiling WDB should be fairly simple, if you have the appropriate libraries and systems installed. The following procedure is based on Ubuntu Lucid; keep in mind that the code changes faster than this wiki page. Install the following debian packages on Precise Pangolin the packages would be:

Coding

anonymous@undisclosed.example.com (Anonymous) — Tue, 31 May 2022 09:29:32 +0000

Coding Although WDB is originally developed and hosted by met.no (), it's a true open-source project under GPL2 license. If you would like to contribute, contact us using the mail address listed in the sidebar. We are currently working on setting up a public mailing list that will be utilized for future development discussions.

Coding Style Guide

anonymous@undisclosed.example.com (Anonymous) — Tue, 31 May 2022 09:29:32 +0000

Coding Style Guide Introduction Standardization is important. When projects follow standards, good things happen: * Different programmers can go into any code, and have a chance to figure out what is going on. * New people can get up to speed quickly.

Development Environment

anonymous@undisclosed.example.com (Anonymous) — Tue, 31 May 2022 09:29:32 +0000

Development Environment This page is under construction. WDB has been developed to be as Eclipse-friendly as possible. The following is a preliminary recipe as to how you can set up Eclipse for WDB (on a Linux environment). To set up the basic development environment used for WDB:

Future Work

anonymous@undisclosed.example.com (Anonymous) — Tue, 31 May 2022 09:29:32 +0000

Future Work The following page will summarize some of the future work discussion for WDB. Scaling Hardware Vertically Vertical scaling: essentially adding more hardware ressources to the same machine (i.e., more and faster processors, memory and disk).

Optimizing WCI

anonymous@undisclosed.example.com (Anonymous) — Tue, 31 May 2022 09:29:32 +0000

Optimizing WCI Optimizing of Query Plan Optimizing of Data Reads Distributed Database Cluster WCI backend memcache The performance data we are seeing indicate that the database is not effectively using the memory it has assigned. We see no significant difference, for instance, between performance of a machine with 8GB and one with 16GB of RAM. The idea here would be - basically - to force reuse of RAM for the database installation. A suggested implementation is given below:

WDB Roadmap

anonymous@undisclosed.example.com (Anonymous) — Tue, 31 May 2022 09:29:32 +0000

WDB Roadmap The WDB roadmap is an attempt to outline what the objectives of the WDB development team are for the next 12 month period. Reality, of course, will not cooperate with us, so we will probably both be late and overly optimistic. Nevertheless, having the roadmap serves a number of purposes:

Testing

anonymous@undisclosed.example.com (Anonymous) — Tue, 31 May 2022 09:29:32 +0000

Testing The details of the test framework for WDB are described in the Test Plan chapter of the Developer Documentation. Specific installation tests for each component of the WDB system are documented in the System Test Specification of the component. Continuous Integration