Why is my risksheet slow to load?
Risksheet loading performance degrades primarily due to high linked-item column count and concurrent multi-user access, not raw data volume. Each linked-item column requires additional Polarion queries to resolve relationships, and multiple simultaneous users compound this load. Large risksheets (500+ work items) with many link columns (10+) and concurrent editing by multiple users will experience noticeable slowdowns. See Slow Page Loading for optimization strategies and Architecture for data loading behavior.When should I split a large risksheet into multiple sheets?
Split risksheets when you experience performance degradation from high linked-item column density combined with multi-user concurrent access. The decision point isn’t a specific row count—it’s the combination of column complexity and simultaneous users. For example, 1000 rows with 3 link columns performs better than 200 rows with 15 link columns when 5 users edit concurrently. Consider splitting when load times exceed 10 seconds or save operations take more than 5 seconds. Organize splits by FMEA type, risk category, or project phase. See Configure Multi-Project Setup for multi-risksheet architecture patterns.How many users can work on a risksheet simultaneously?
Concurrent user count impacts performance more than data volume—3-5 simultaneous editors on a heavily-linked risksheet will cause noticeable slowdowns even with moderate row counts. The scalability threshold depends on linked-item column count: risksheets with 5+ link columns degrade faster as concurrent users increase. For optimal performance, limit simultaneous editors to 3-5 users per risksheet, or reduce link column count if more concurrent access is required. See Working Sessions for session management and Performance Questions for optimization guidance.Does data volume affect performance more than configuration?
No—configuration complexity (especially linked-item column count) impacts performance more than raw data volume. A risksheet with 200 rows and 15 linked-item columns loads slower than one with 1000 rows and 3 link columns because each link column triggers separate Polarion queries. Calculated columns, custom renderers, and complex formulas also add overhead beyond simple data display. Focus optimization on reducing link column count and simplifying configuration before worrying about row count. See Configure Calculated Columns and Customize Link Rendering for performance-conscious configuration.How do I optimize export performance?
Export performance degrades with merged cells, complex formatting, and large linked-item datasets. PDF and Excel exports process merged cells inefficiently, causing slowdowns on risksheets with extensive merged cell configurations. To optimize: minimize merged cells, reduce visible columns during export using Control Column Visibility in Exports, and consider exporting smaller subsets by filtering before export. Pre-calculated columns export faster than dynamic formulas. See Export Performance Issues for detailed optimization strategies.Can Polarion server configuration affect RISKSHEET performance?
Yes—Polarion server misconfiguration, insufficient memory allocation, or database performance issues can significantly impact RISKSHEET loading and saving operations. RISKSHEET relies on Polarion’s work item query engine and relationship resolution, so Polarion server bottlenecks directly affect RISKSHEET. Check Polarion server logs for slow queries, verify adequate JVM heap size, and ensure database indexes are optimized. Contact Nextedy support if performance issues persist after risksheet optimization. See Troubleshoot Administration Issues for server-level diagnostics.For large-scale deployments, organize risksheets by domain: